From: Bernt Hansen <bernt@norang.ca>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>, Jambunathan K <kjambunathan@gmail.com>
Subject: Re: update of snapshot release broken?
Date: Sun, 24 Oct 2010 09:58:49 -0400 [thread overview]
Message-ID: <8739rvsndy.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <AANLkTimo29NsJZ9uvK+ALY-hzMq6Uf0F0AQigGq4GtRg@mail.gmail.com> (Michael Brand's message of "Sun, 24 Oct 2010 14:21:18 +0200")
Michael Brand <michael.ch.brand@gmail.com> writes:
> On Sun, Oct 24, 2010 at 13:09, Jambunathan K <kjambunathan@gmail.com> wrote:
>> git archive --format=tar --prefix=project/ HEAD | gzip >latest.tar.gz
>
> Thanks, that helps me already to install the currently very latest
> version to a different machine at some time later. But even better for
> me would be to git-pull the very latest version on one machine, get
> its SHA1 and then do a git-whatever with the same SHA1 at some time
> later on another machine to get the same version again.
git pull on one machine
git describe to get short SHA1
git checkout SHA1 on other machine
should give you exactly the same codebase on each.
Example:
$ git checkout origin/master # on machine 1
$ git describe
release_7.01h-823-gd600831 # Note SHA1 starting here
^^^^^^^
# SHA1 is d600831
# On other machine
$ git pull # to get up to date code
$ git checkout d600831
And you have the same commit on both machines.
With this method you can also backup and move to any arbitrary commit in
the history -- if you find you have a bug in the current code that was
introduced 5 commits ago, you can back up to a previous commit (the one
before the one introducing the bug) and keep working.
HTH,
Bernt
next prev parent reply other threads:[~2010-10-24 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 7:40 update of snapshot release broken? Michael Brand
2010-10-24 10:41 ` Jambunathan K
2010-10-24 10:57 ` Jambunathan K
2010-10-24 12:19 ` Michael Brand
2010-10-24 15:05 ` Jambunathan K
2010-10-24 19:12 ` Michael Brand
2010-10-24 11:09 ` Jambunathan K
2010-10-24 12:21 ` Michael Brand
2010-10-24 13:58 ` Bernt Hansen [this message]
2010-10-24 17:44 ` Michael Brand
2010-10-24 12:56 ` Andreas Röhler
2010-10-27 22:10 ` Bastien
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8739rvsndy.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=michael.ch.brand@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).