also sprach Felix Kaiser [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 the reposit
On Wed, Mar 23, 2011 at 11:50 AM, martin f krafft wrote:
>
> also sprach Dieter Plaetinck [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
also sprach Dieter Plaetinck [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 public API. It'
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 wrote:
>
> > also sprach Dieter Plaetinck [2011.03.20.1235
> > +0100]:
> > > oh, one more thing.
> > > you can query the current branch in a pure-python way, by
> > > reading
On Wed, 23 Mar 2011 08:00:27 +0100
martin f krafft wrote:
> also sprach Dieter Plaetinck [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 ||
also sprach Dieter Plaetinck [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 | http://madduck.net/ | http://two.sen
Arch Linux users rejoice
Rene's awesome program is now only a `clyde -S dvcs-autosync-git` away.
http://aur.archlinux.org/packages.php?ID=47643
Rene is working on Debian/Ubuntu packages.
Dieter
___
vcs-home mailing list
vcs-home@lists.madduck.net
http:
Am Sonntag, 20. März 2011, um 12:26:36 schrieb Dieter Plaetinck:
> Either way I don't think we should query the remote for "what do you have",
> frankly we shouldn't care. we only care about pushing (explicitly enough)
> the thing that we need to push.
Agreed.
> If you only want to support a m
On Sun, 20 Mar 2011 12:26:36 +0100
Dieter Plaetinck wrote:
> On Sun, 20 Mar 2011 08:31:39 +0100
> René Mayrhofer 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
On Sun, 20 Mar 2011 08:31:39 +0100
René Mayrhofer 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 and none spec
Am Freitag, 18. März 2011, 22:59:07 schrieb Dieter Plaetinck:
> I found sparkleshare very disappointing. I spent more time reporting bugs
> for all kinds of stupid things then actually using the software.. I got it to
> sync 1 file then it stopped and I gave up.
> https://github.com/hbons/Sparkl
On Sat, 19 Mar 2011 21:18:24 +0100
René Mayrhofer wrote:
> 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
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 patche
On Sat, 19 Mar 2011 20:26:43 +0100
René Mayrhofer wrote:
> Done and pushed --force to gitorious. Whoever cloned the repo, please discard
> the local history and clone afresh. This was painful and took me about 4h to
> go through. I therefore hope it was worth it and that I will receive many
>
Am Dienstag, 15. März 2011, 10:05:17 schrieb Dieter Plaetinck:
> On Mon, 14 Mar 2011 15:53:44 -0500
> "Chanoch (Ken) Bloom" 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 as
On Fri, 18 Mar 2011 22:59:07 +0100
Dieter Plaetinck wrote:
> To round off:
> 1) What's the idea behind autosync-server? doesn't the xmpp method work just
> fine?
I can answer this one myself now. the README section mentions you had the
idea of using a simple tcp protocol. or "whatever sparkles
Today I tried out bouth sparkleshare and dvcs-autosync.
I found sparkleshare very disappointing. I spent more time reporting bugs for
all kinds of stupid things then actually using the software.. I got it to sync
1 file then it stopped and I gave up.
https://github.com/hbons/SparkleShare/issues
Am 2011-03-14 21:53, schrieb Chanoch (Ken) Bloom:
> First, run `git filter-branch` with the `--prune-empty` option to get
> rid of the empty commits that used to contain only changes to the .pyc
> file.
I think I already did that, but will need to double-check.
> Second, rewriting the history to b
On Mon, 14 Mar 2011 15:53:44 -0500
"Chanoch (Ken) Bloom" 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 as "autocommit"? why do you
> > >commit .pyc files?
> > .pyc removed from his
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 go
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 enough to properly change the past commit
messages and merge them for
Dear Antonio,
On 11.03.2011 10:16, Antonio Ospite wrote:
What does it do?
Automatically keep DVCS repositories in sync whenever changes happen by
automatically committing and pushing/pulling.
I like this distributed sync approach, however I can see cases where
automati
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 its
On Mon, 14 Mar 2011 17:02:01 +0100
René Mayrhofer 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 changes committed as
Am 2011-03-12 21:25, schrieb seanh:
> This sounds great! One thought: I think in many use-cases lots of small
> changes to a file will be saved one after another and then no changes
> for a while, or else lots of files will be changed in a short time and
> then no changes for a while. It sounds lik
Am 2011-03-13 17:21, schrieb Dieter Plaetinck:
> very cool project.
Thanks ;)
> 1) about the xmpp stuff. can i use my jabber.org account (which I use to IM)
> for this? can i have multiple systems log in to that? will that cause IM's
> from friends to get sent to those jabberbots instead of my
very cool project.
1) about the xmpp stuff. can i use my jabber.org account (which I use to IM)
for this? can i have multiple systems log in to that? will that cause IM's
from friends to get sent to those jabberbots instead of my chat program? Would
you recommend this, or should i make a seco
On Wed, Mar 09, 2011 at 09:17:07PM +0100, René Mayrhofer wrote:
> How does it do it? 0. Set up desktop
> notifications (for these nice bubble-style popups when anything
> happens) and log into a Jabber/XMPP account specified in the config
> file.
>
> 1. Monitor a specific
On Wed, 9 Mar 2011 21:17:07 +0100
René Mayrhofer wrote:
>
> What does it do?
>
> Automatically keep DVCS repositories in sync whenever changes happen by
> automatically committing and pushing/pulling.
>
I like this distributed sync approach, however I can see cases wh
Hi everybody,
So far, I was only an avid lurker on this list, but have not yet found time to
contribute myself. With this email, I hope to change this and attach a preview
of a Python script/daemon that I have been meaning to release for ages, but
haven't gotten around to do so. In short, it do
30 matches
Mail list logo
