From: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
To: Zack Brown <zbrown@tumblerings.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: cg-seek messed me up
Date: Tue, 31 May 2005 16:45:07 +0200 [thread overview]
Message-ID: <20050531144506.GC6706@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <20050531143318.GB27047@tumblerings.org>
Hello,
this is exactly why I don't use it at the moment. My own frontend does
before every pull/push/merge/commit a 'look for dirty files and look for
uncommited deltas'.
Thomas
next prev parent reply other threads:[~2005-05-31 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 14:33 cg-seek messed me up Zack Brown
2005-05-31 14:45 ` Thomas Glanzmann [this message]
2005-05-31 15:23 ` randy_dunlap
2005-05-31 18:39 ` Petr Baudis
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=20050531144506.GC6706@cip.informatik.uni-erlangen.de \
--to=sithglan@stud.uni-erlangen.de \
--cc=git@vger.kernel.org \
--cc=zbrown@tumblerings.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