All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Obtaining old SVN revision
Date: Wed, 13 May 2009 13:51:13 +0200	[thread overview]
Message-ID: <87r5ytrzke.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4A0AA1D9.1030808@carallon.com> (Will Wagner's message of "Wed\, 13 May 2009 11\:32\:57 +0100")

>>>>> "Will" == Will Wagner <will_wagner@carallon.com> writes:

 Will> Hello all,

 Will> Following the transition to git how can I checkout buildroot to
 Will> a specific SVN revision?

 Will> I had hoped that the SVN repository would remain read only for a while
 Will> but it seems to have gone away. Presumably I can clone git and then
 Will> checkout back to the revision I want, I'm just not sure how to specify
 Will> that in git. Do I just have to work out what date the SVN revision
 Will> was?

Hmm, that's a mistake - svn should continue to work (read only). I'll
check with the osuosl.org guys. We don't have any links with the
correspondence between svn and git revisions, but I still have my
git-svn tree, so if you give me the svn rev, then I'll look up the
corresponding git revision.

You can checkout older git revisions with git checkout <rev>. Normally
you can also use the date based syntax (see man git-rev-parse) like:

git show @{2009-05-01}, but the commit dates are not correct for the
pre-git commits.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-05-13 11:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 10:32 [Buildroot] Obtaining old SVN revision Will Wagner
2009-05-13 11:51 ` Peter Korsgaard [this message]
     [not found]   ` <4A0ABA5D.7040308@free.fr>
2009-05-13 12:21     ` Peter Korsgaard
2009-05-13 13:27       ` Cyril HAENEL
2009-05-13 13:41         ` Peter Korsgaard

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=87r5ytrzke.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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.