also sprach Stéphane Glondu <[EMAIL PROTECTED]> [2008.09.30.1159 +0200]:
> Sorry, I didn't pay attention to this. I guess this needs a special
> cloning/pushing/pulling procedure, then?

Yes, and that would be setup by tg-remote, which already sets this
up for refs/top-bases/*.

> BTW, you don't talk about pushing/pulling/sharing with others in
> your quick tuto (but you do talk about cloning).

tg-export should make this all transparent, i.e. you should be able
to push your branches like before, and top-bases will also be

The nice thing about topgit is that it's really just a thin layer on
top of Git, so everything Git also works with TopGit.

> > [...] First of all, this clearly seems like a feature
> > for upstream, [...] 
> What do you mean by "a feature for upstream"?

Tagging previous version of topic branches/patches.

> > [...] and second, Git is all about keeping track of refs,
> > storing them as payload in a branch seems like patching patch files
> > :)
> Indeed, it seems so. But I was getting inspiration from
> pristine-tar. I guess *.id files that are committed there are not
> meant to be used (and/or alterable) by human beings. Do we want
> this for "historical" bases and tips of tg branches? I am not
> really at ease with mixing "live" and "dead" script-manipulated
> references in the same place.

I am sure pristine-tar could be redesigned to git in with Git

 .''`.   martin f. krafft <[EMAIL PROTECTED]>
: :'  :  proud Debian developer, author, administrator, and user
`. `'` -
  `-  Debian - when you have better things to do than fixing systems
now I lay me back to sleep.
the speaker's dull; the subject's deep.
if he should stop before I wake,
give me a nudge for goodness' sake.

Attachment: digital_signature_gpg.asc
Description: Digital signature (see

vcs-pkg-discuss mailing list

Reply via email to