also sprach Dieter Plaetinck die...@plaetinck.be [2011.03.20.1235 +0100]:
oh, one more thing.
you can query the current branch in a pure-python way, by reading .git/HEAD
No, please do not use this. Use
git symbolic-ref -q HEAD || git name-rev --name-only HEAD
--
martin |
Am Mittwoch, 23. März 2011, um 09:33:37 schrieb Dieter Plaetinck:
On Wed, 23 Mar 2011 08:00:27 +0100
martin f krafft madd...@madduck.net wrote:
also sprach Dieter Plaetinck die...@plaetinck.be [2011.03.20.1235
+0100]:
oh, one more thing.
you can query the current branch in a
also sprach Dieter Plaetinck die...@plaetinck.be [2011.03.23.0933 +0100]:
well, the idea behind doing it in pure-python is removing the
overhead of spawning extra processes, do you have an argument why
reading the branchname of the current HEAD in a few lines of
python is bad?
.git/* is not a
On Wed, Mar 23, 2011 at 11:50 AM, martin f krafft madd...@madduck.net wrote:
also sprach Dieter Plaetinck die...@plaetinck.be [2011.03.23.0933 +0100]:
well, the idea behind doing it in pure-python is removing the
overhead of spawning extra processes, do you have an argument why
reading the
also sprach Felix Kaiser felix.kai...@fxkr.net [2011.03.23.1250 +0100]:
.git/* is not a public API. It's considered internal.
Not its not.
Its even documented[1]: ... a valid git repository must have the
HEAD file; some porcelains may use it to guess the designated
default branch of
On Sun, 20 Mar 2011 08:31:39 +0100
René Mayrhofer r...@mayrhofer.eu.org wrote:
Am Freitag, 18. März 2011, 22:59:07 schrieb Dieter Plaetinck:
Note if you do this, server:test.git won't actually have a master branch
yet.
So when i touch ~/autosync/test, I get this:
No refs in common
Am Dienstag, 15. März 2011, 10:05:17 schrieb Dieter Plaetinck:
On Mon, 14 Mar 2011 15:53:44 -0500
Chanoch (Ken) Bloom kbl...@gmail.com wrote:
On Mon, Mar 14, 2011 at 08:53:03PM +0100, Rene Mayrhofer wrote:
On 14.03.2011 17:15, Dieter Plaetinck wrote:
why are many code changes committed
Am Samstag, 19. März 2011, 20:33:08 schrieb Dieter Plaetinck:
that person was me. as you can see, i already have a bunch of patches queued
up in a pull request on gitorious.
i'll treat it as a git exercise for myself to port my patches to the new
history branch.
I already saw the patches
On Mon, 14 Mar 2011 17:02:01 +0100
René Mayrhofer r...@mayrhofer.eu.org wrote:
Btw, the project is now online at http://gitorious.org/dvcs-autosync
and should even include the full history (already close to a year,
although with very irregular commit intervals ;-) ).
ugh.
why are many code
On 14.03.2011 17:15, Dieter Plaetinck wrote:
ugh.
why are many code changes committed as autocommit? why do you
commit .pyc files? why do you use meaningless commit messages like
move another file ?
Well, it is the full history so far, and that includes the autocommits
made by the script itself
On Mon, Mar 14, 2011 at 08:53:03PM +0100, Rene Mayrhofer wrote:
On 14.03.2011 17:15, Dieter Plaetinck wrote:
why are many code changes committed as autocommit? why do you
commit .pyc files?
.pyc removed from history with --force push to gitorious done.
However, my git-fu is not yet good
11 matches
Mail list logo
