git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maaartin <grajcar1@seznam.cz>
To: git@vger.kernel.org
Subject: Problems switching branches
Date: Wed, 3 Nov 2010 02:37:31 +0000 (UTC)	[thread overview]
Message-ID: <loom.20101103T032930-451@post.gmane.org> (raw)

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?

             reply	other threads:[~2010-11-03  2:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03  2:37 Maaartin [this message]
2010-11-04  0:23 ` Problems switching branches Maaartin
2010-11-04 14:39   ` Nguyen Thai Ngoc Duy
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=loom.20101103T032930-451@post.gmane.org \
    --to=grajcar1@seznam.cz \
    --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).