From: Petr Baudis <pasky@suse.cz>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Subversion-style incrementing revision numbers
Date: Wed, 20 Sep 2006 00:11:11 +0200 [thread overview]
Message-ID: <20060919221111.GF8259@pasky.or.cz> (raw)
In-Reply-To: <eeppkl$rm9$2@sea.gmane.org>
Dear diary, on Wed, Sep 20, 2006 at 12:07:08AM CEST, I got a letter
where Jakub Narebski <jnareb@gmail.com> said that...
> Joel Dice wrote:
> > Rationale:
> >
> > Incrementing revision numbers (IRNs - an acronym I just made up) are
> > useful in that they can be treated as auto-generated tags which are easier
> > to remember and communicate than SHA hashes, yet do not require extra
> > effort to create like real tags. Also, they have the advantage of being
> > chronologically ordered, so if I assert that a bug was fixed in revision
> > 42 of a shared repository, everyone may assume that revision 45 has that
> > fix as well.
>
> That is true _only_ if you have linear history. If you have multiple
> concurrent branches, revision 42 can be in branch 'next', revision '45' in
> topic branch 'xx/topic' which forked before revision 42, and do not have
> the fix.
Oops, I've completely overlooked that bit of the rationale. Of course
IRNs cannot assure this.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Snow falling on Perl. White noise covering line noise.
Hides all the bugs too. -- J. Putnam
next prev parent reply other threads:[~2006-09-19 22:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 21:07 Subversion-style incrementing revision numbers Joel Dice
2006-09-19 21:18 ` Petr Baudis
2006-09-19 21:42 ` Joel Dice
2006-09-19 22:00 ` Petr Baudis
2006-09-19 22:24 ` Joel Dice
2006-09-19 22:33 ` Shawn Pearce
2006-09-19 22:40 ` Johannes Schindelin
2006-09-19 22:39 ` Shawn Pearce
2006-09-19 21:58 ` Jakub Narebski
2006-09-19 21:51 ` Linus Torvalds
2006-09-19 22:06 ` Petr Baudis
2006-09-19 22:20 ` Linus Torvalds
2006-09-19 23:35 ` Joel Dice
2006-09-20 0:15 ` Jakub Narebski
2006-09-20 16:13 ` Joel Dice
2006-09-20 7:46 ` Junio C Hamano
2006-09-20 17:28 ` Robin Rosenberg
2006-09-20 18:22 ` Petr Baudis
2006-09-20 19:07 ` Junio C Hamano
2006-09-19 22:07 ` Jakub Narebski
2006-09-19 22:11 ` Petr Baudis [this message]
2006-09-19 22:17 ` Jakub Narebski
2006-09-19 23:07 ` Joel Dice
2006-09-19 22:18 ` Shawn Pearce
2006-09-19 22:23 ` Shawn Pearce
2006-09-19 22:30 ` Joel Dice
2006-09-19 22:09 ` Shawn Pearce
2006-09-19 22:40 ` Joel Dice
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=20060919221111.GF8259@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).