From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] Saul Wold : opkg-utils: convert to git repo at git.yoctoproject.org
Date: Thu, 09 Feb 2012 23:35:28 +0000 [thread overview]
Message-ID: <1328830528.2716.305.camel@x121e.pbcl.net> (raw)
In-Reply-To: <20120209223044.GF10322@jama.jama.net>
On Thu, 2012-02-09 at 23:30 +0100, Martin Jansa wrote:
> Why +git when we have +svnr not +svn? and both systems call it revision?
>
> Wouldn't it be more consistent to use +gitr and then also we wouldn't
> have this problem with PV going backwards..
The "svnrNNNN" name came about because the Subversion convention is that
revisions are always named "r1982" or whatever. Git doesn't do that, it
just uses the hash directly, so it would be more natural to just write
"+gitNNNNN". Adding an extra "r" in there doesn't contribute any useful
information.
All that said, though, this seems like a fairly trivial issue and I
don't think there is any good reason to go around changing existing
recipes just to "fix" the version strings.
p.
prev parent reply other threads:[~2012-02-09 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120201151531.BE60410330@opal>
2012-02-01 15:37 ` [oe-commits] Saul Wold : opkg-utils: convert to git repo at git.yoctoproject.org Martin Jansa
2012-02-09 22:07 ` Saul Wold
2012-02-09 22:30 ` Martin Jansa
2012-02-09 22:59 ` Khem Raj
2012-02-09 23:14 ` Richard Purdie
2012-02-09 23:35 ` Phil Blundell [this message]
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=1328830528.2716.305.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.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