All of lore.kernel.org
 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 22:12:35 -0700	[thread overview]
Message-ID: <20050712051235.GA10930@buici.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0507112149290.17536@g5.osdl.org>

On Mon, Jul 11, 2005 at 09:59:25PM -0700, Linus Torvalds wrote:
> 
> 
> On Mon, 11 Jul 2005, Marc Singer wrote:
> > 
> > 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?
> 
> It's really a flow of commits. Nothing will ever really remember what the 
> starting point was at some later date if you have done commits, and the 
> branch will always follow the _head_ of development on that branch.

That's the important detail.

As an aside, we (a vary large set of developers) have been using SCM
tools for how-many-freakin-years and only now am I seeing something
sane.  Cheers.

  reply	other threads:[~2005-07-12  5:13 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
2005-07-12  4:59                     ` Linus Torvalds
2005-07-12  5:12                       ` Marc Singer [this message]
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=20050712051235.GA10930@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.