From: "Bryan Wu" <cooloney.lkml@gmail.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: "Bryan Wu" <bryan.wu@analog.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] [Scripts] add svn revision information to setlocalversion
Date: Thu, 31 Jan 2008 00:00:44 +0800 [thread overview]
Message-ID: <386072610801300800r5dfe3b21l56a0f8a4184842d3@mail.gmail.com> (raw)
In-Reply-To: <20080130102442.GB20846@uranus.ravnborg.org>
On Jan 30, 2008 6:24 PM, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Wed, Jan 30, 2008 at 06:15:25PM +0800, Bryan Wu wrote:
> > Signed-off-by: Bryan Wu <bryan.wu@analog.com>
> > ---
> > scripts/setlocalversion | 4 ++++
> > 1 files changed, 4 insertions(+), 0 deletions(-)
> >
> > diff --git a/scripts/setlocalversion b/scripts/setlocalversion
> > index 52f032e..2d6645c 100644
> > --- a/scripts/setlocalversion
> > +++ b/scripts/setlocalversion
> > @@ -25,6 +25,10 @@ if head=`git rev-parse --verify HEAD 2>/dev/null`; then
> > # All done with git
> > exit
> > fi
> > +# Check for svn and a svn repo.
> > +if rev=`svn info 2>/dev/null | grep '^Revision' | awk '{print $NF}'` ; then
> > + printf -- '-svn%s' $rev
> > +fi
> >
> > # Check for mercurial and a mercurial repo.
> > if hgid=`hg id 2>/dev/null`; then
>
> Hi Bryna.
>
> Can I ask you to change the shell script to use
> a chained if so if we find git we do not try mercurial nor svn.
>
Do you mean follow the git and mercurial style to rewrite this svn patch?
No problem I will update it.
> I should have done so initially when adding the patch with mercurial
> support but it slipped my mind.
>
We add svn to this for some time, but I forget to sent it out.
Now I hope it can fix this hole.
Thanks
-Bryan
next prev parent reply other threads:[~2008-01-30 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 10:15 Bryan Wu
2008-01-30 10:24 ` Sam Ravnborg
2008-01-30 16:00 ` Bryan Wu [this message]
2008-01-30 16:39 ` [PATCH 1/1 try#2] " Bryan Wu
2008-02-02 18:24 ` Sam Ravnborg
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=386072610801300800r5dfe3b21l56a0f8a4184842d3@mail.gmail.com \
--to=cooloney.lkml@gmail.com \
--cc=bryan.wu@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®