git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: "stgit clean" has problems with removed generated files
Date: Fri, 24 Nov 2006 09:20:35 +0100	[thread overview]
Message-ID: <ek69tf$bp9$1@sea.gmane.org> (raw)
In-Reply-To: 20061123192831.GL5443@nan92-1-81-57-214-146.fbx.proxad.net

Yann Dirson wrote:

> On Thu, Nov 23, 2006 at 04:33:42PM +0000, Catalin Marinas wrote:
>> >fatal: Untracked working tree file 'include/asm-arm/constants.h' would be  
>> >overwritten by merge.
>> 
>> That's a git error and I think it is the correct behaviour. It is
>> safer to notify that a local file is overridden by a merge/switch
>> operation rather than just losing its content.
> 
> Right, I do not discuss the behaviour of git here.  But when I first
> encountered this issue, I was really wondering about what was
> happenning.  It would be really helpful in such a case, if stgit was
> able to pinpoint the precise patch which could not be popped.  It could
> also be helpful to tell when popping patches - currently it's done
> "behind my back", and I could only understand what was happenning by
> reading the code.

I think it was corrected in git, or is being corrected (meaning it is
in 'next' or in 'pu'); it being relaxing "would be overwritten by merge"
check for files which were, but are not, under version control.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git


  reply	other threads:[~2006-11-24  8:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23 16:11 "stgit clean" has problems with removed generated files Yann Dirson
2006-11-23 16:33 ` Catalin Marinas
2006-11-23 19:28   ` Yann Dirson
2006-11-24  8:20     ` Jakub Narebski [this message]
2006-12-06 13:12     ` Catalin Marinas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ek69tf$bp9$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).