git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Maaartin <grajcar1@seznam.cz>
Cc: git@vger.kernel.org
Subject: Re: Problems switching branches
Date: Thu, 4 Nov 2010 21:39:49 +0700	[thread overview]
Message-ID: <AANLkTikK93Jt+dAkpp6K-hQEo6D67q5OKJSLs+g0YL4y@mail.gmail.com> (raw)
In-Reply-To: <loom.20101104T012032-963@post.gmane.org>

On Thu, Nov 4, 2010 at 7:23 AM, Maaartin <grajcar1@seznam.cz> wrote:
> Maaartin <grajcar1 <at> seznam.cz> writes:
>
>>
>> I sometimes run in a problem similar to
>> http://kerneltrap.org/mailarchive/git/2008/10/15/3667644/thread
>> There are some ignored files which I want neither track nor throw away; I'm
> just
>> happy to have them and keep them out of version control.
>>
>> Unfortunately, there weren't ignored in the old branch. I'd be quite happy
> with
>> non-destructive switching like "checkout everything what doesn't overwrite an
>> untracked file", so I would end in the old branch with a dirty working tree.
> Is
>> it possible?
>
> No answer?

Which means nobody is interested in. Well, not really.

I also get irritated by a similar situation, where the untracked files
have the same content as the to-be-checked-out files. I have been
tempted (but never got around) to make git compare the in-index
content and the untracked file, if it's the same, no need to abort the
checkout process.

But your approach may be better. Yes, I think it's possible. Any
suggestion for checkout's new argument? --no-overwrite-untracked seems
too long.
-- 
Duy

  reply	other threads:[~2010-11-04 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03  2:37 Problems switching branches Maaartin
2010-11-04  0:23 ` Maaartin
2010-11-04 14:39   ` Nguyen Thai Ngoc Duy [this message]
2010-11-05  6:36     ` Maaartin-1
2010-11-05  8:41       ` Nguyen Thai Ngoc Duy
2010-11-24 22:33       ` Neal Kreitzinger

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=AANLkTikK93Jt+dAkpp6K-hQEo6D67q5OKJSLs+g0YL4y@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=grajcar1@seznam.cz \
    /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).