From: Maaartin <grajcar1@seznam•cz>
To: git@vger•kernel.org
Subject: Re: Commiting automatically (2)
Date: Tue, 21 Dec 2010 08:36:30 +0000 (UTC) [thread overview]
Message-ID: <loom.20101221T092948-59@post.gmane.org> (raw)
In-Reply-To: 20101220073312.GA23482@nibiru.local
Enrico Weigelt <weigelt <at> metux.de> writes:
> * Maaartin <grajcar1 <at> seznam.cz> wrote:
>
> > Yes, I wonder why it wasn't already implemented. I do something like
> > make all; git snapshot; send_the_executable_to_the_customer
> > which is IMHO needed quite often.
>
> Perhaps it's wise to just use a separate repository on the same
> repository. Maybe make it more convenient using some little
> shell functions. I'm also using that for backup purposes, where
> the repo lies outside the to-be-backed-up tree.
I considered using a separate repository, too, but having "all in one" feels
somehow better. It allows me to push everything to a single remote repo and
compare the snapshots to ordinal commits, etc.
I let the snapshot point to the current head, which is where I get a problem now:
git show-ref HEAD
returns nothing,
git show-ref --head
returns HEAD and all branches and tags. Isn't it a bug? How can I get the HEAD
reference? I'm using git version 1.7.2.3 on cygwin.
next prev parent reply other threads:[~2010-12-21 8:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 8:29 Commiting automatically (2) Maaartin
2010-12-19 15:08 ` Taylor Hedberg
2010-12-19 18:36 ` Jonathan Nieder
2010-12-19 20:17 ` Jonathan Nieder
2010-12-20 5:12 ` Maaartin
2010-12-19 19:32 ` Junio C Hamano
2010-12-20 5:46 ` Maaartin
2010-12-20 7:33 ` Enrico Weigelt
2010-12-21 8:36 ` Maaartin [this message]
2010-12-21 13:06 ` Jakub Narebski
[not found] ` <4D1190A6.4070201@seznam.cz>
2010-12-27 12:04 ` Jakub Narebski
2011-01-03 0:39 ` Maaartin-1
2011-01-03 17:34 ` Jakub Narebski
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=loom.20101221T092948-59@post.gmane.org \
--to=grajcar1@seznam$(echo .)cz \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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