git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Ron Garret <ron1@flownet.com>
Cc: git@vger.kernel.org
Subject: Re: Individual file snapshots
Date: Fri, 12 Feb 2010 21:41:42 +0100	[thread overview]
Message-ID: <4B75BD06.1010802@lsrfire.ath.cx> (raw)
In-Reply-To: <ron1-CD3223.04030512022010@news.gmane.org>

Am 12.02.2010 13:03, schrieb Ron Garret:
> Before I reinvent the wheel...
> 
> I would like to be able to store snapshots of individual files without 
> making a commit on the main branch.  The scenario is that I've written 
> some experimental code that I have decided not to keep as part of the 
> main project, but which I might want to refer back to some day.  Is 
> there any easy way of doing that in git?

You could keep the experimental files (or changes) in a separate,
private branch on your local repository.

René

  parent reply	other threads:[~2010-02-12 20:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12 12:03 Individual file snapshots Ron Garret
2010-02-12 12:18 ` Peter Krefting
2010-02-12 17:24   ` Ron Garret
2010-02-12 20:41 ` René Scharfe [this message]
2010-02-12 21:25   ` Ron Garret
2010-02-12 21:37     ` Brian Gernhardt
2010-02-12 21:57       ` Ron Garret
2010-02-12 22:14         ` Junio C Hamano
2010-02-12 22:41           ` Ron Garret
2010-02-12 22:32         ` Brian Gernhardt
2010-02-12 22:39           ` Ron Garret
2010-02-13  0:33             ` Mark Lodato
2010-02-13  0:47               ` Junio C Hamano
2010-02-13 15:13                 ` Mark Lodato
2010-02-13 18:41                   ` Ron Garret
2010-02-13 18:58                   ` Junio C Hamano
2010-02-13  7:01               ` Ron Garret
2010-02-13  3:00         ` Larry D'Anna

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=4B75BD06.1010802@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=git@vger.kernel.org \
    --cc=ron1@flownet.com \
    /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).