git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Singer <elf@buici.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Bootstrapping into git, commit gripes at me
Date: Mon, 11 Jul 2005 21:43:53 -0700	[thread overview]
Message-ID: <20050712044352.GA9919@buici.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0507112132170.17536@g5.osdl.org>

On Mon, Jul 11, 2005 at 09:34:33PM -0700, Linus Torvalds wrote:
> 
> 
> On Mon, 11 Jul 2005, Linus Torvalds wrote:
> > 
> >     Of course, if you want to create a new branch "my-branch" and _not_
> >     check it out, you could have done so with just
> > 
> >         git-rev-parse v2.6.12^0 > .git/refs/heads/my-branch
> > 
> >     which I think I will codify as "git branch".
> 
> And now we have that "git branch". It's a trivial one-liner, except with
> the setup and error checking it's actually more like six lines.

Does it make sense to think about this branch as an flow of commits?
Or is it just a starting point for a line of development?  If I make a
branch, check it out, commit changes to it, and then clobber the
working directory, can I later resume that branch of development
without creating a new branch?  Do I need to set a tag to mark the
last commit on that branch?

  reply	other threads:[~2005-07-12  4:44 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08 23:07 Bootstrapping into git, commit gripes at me Marc Singer
     [not found] ` <7v4qb46dff.fsf@assigned-by-dhcp.cox.net>
2005-07-09  1:11   ` Marc Singer
2005-07-09 21:04     ` Matthias Urlichs
2005-07-10 15:06       ` Petr Baudis
     [not found]   ` <20050709003636.GA26526@buici.com>
     [not found]     ` <7v1x684wgr.fsf@assigned-by-dhcp.cox.net>
2005-07-09  1:16       ` Marc Singer
2005-07-09  1:31         ` Junio C Hamano
2005-07-09  1:43 ` Linus Torvalds
2005-07-11 22:20   ` Marc Singer
2005-07-11 23:03     ` Junio C Hamano
2005-07-11 23:15       ` Junio C Hamano
2005-07-12  0:57       ` Linus Torvalds
2005-07-12  1:43         ` Linus Torvalds
2005-07-12  2:10           ` Marc Singer
2005-07-12  3:09             ` Linus Torvalds
2005-07-12  3:49               ` Linus Torvalds
2005-07-12  4:34                 ` Linus Torvalds
2005-07-12  4:43                   ` Marc Singer [this message]
2005-07-12  4:59                     ` Linus Torvalds
2005-07-12  5:12                       ` Marc Singer
2005-07-12  7:48                   ` Petr Baudis
2005-07-12  9:07                     ` Junio C Hamano
2005-07-12 16:29                       ` Matthias Urlichs
2005-07-24  8:57                       ` Petr Baudis
2005-07-24 16:24                         ` Junio C Hamano
2005-07-12 16:48                     ` Linus Torvalds
2005-08-12  1:26                       ` Petr Baudis
2005-07-12  2:21           ` Junio C Hamano
2005-07-12  3:18             ` Linus Torvalds
2005-07-12  3:41               ` Junio C Hamano
2005-07-12  3:52                 ` Linus Torvalds
2005-07-12  3:53                 ` Marc Singer
2005-07-12 17:04             ` Daniel Barkalow
2005-07-11 23:45     ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2005-07-09  0:40 Marc Singer

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=20050712044352.GA9919@buici.com \
    --to=elf@buici.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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).