[darcs-users] tracking a push

[Zack Brown]

On Thu, Aug 07, 2003 at 08:34:30PM -0400, David Roundy wrote:
> On Thu, Aug 07, 2003 at 09:08:17AM -0700, Zack Brown wrote:
> > I pushed a patch to you, called
> > standardize_paragraph_title_formatting-zbrown9tumblerings.org-Tue_Jul_29_08.47.06_PDT_2003
> > 
> > It wasn't much, just a little documentation stuff, mainly to start
> > experimenting with darcs itself. The thing is, I'm not sure how to check
> > if you applied it. I'm not really concerned with that particular patch,
> > since like I say, it wasn't anything much, but I'm interested in how to
> > deal with this kind of situation.
> >
> > Ideally, I'd like to be able to (in no particular order):
> > 
> > a) check if a maintainer applied a patch they've received via 'push'
> 
> 
> One way is to use the cgi interface to browse the repo:
> 
> http://www.abridgegame.org/cgi-bin/darcs?darcs**
> 
> shows that this patch is already applied.

Yes indeed. That's a good URL.

One thing: I went there and clicked on a patch, taking me to the list of
files. But clicking on one of the files just took me to a blank page...

> 
> Another way would be to try pushing a second time (see answer to b)...
> 
> > b) push the same patch again
> 
> You can just do darcs push again to push again.  If the patch has not yet
> been applied, you will get prompted again to push it.  If you aren't
> prompted, then it means the patch has been applied.  Darcs has no memory of
> previous pushes, it just checks what patches your repo has that the repo
> you're pushing to is missing, and asks which of those you'd like to push.

OK, I see what was confusing me. You'd already accepted the patch and I
didn't realize it, so I thought pushing just only worked once. Now it
makes sense.

> 
> > c) tell darcs to un-push any patches that have not been applied
> > upstream, i.e. tell darcs to locally believe it has not pushed those
> > patches. But darcs should be able to do this without my having to list
> > off all the patches I want unpushed. It should base its operation on the
> > differences between our two repositories.
> 
> Once the patch is pushed, you can't unpush it, since pushing involves
> sending an email (that can't be unsent).  I could introduce a kind of
> 'cancellation' email, that mentions patches you don't want pushed after
> all, but I'm not sure how useful that would be...

Maybe not very, especially since it turns out to be easy to see whether
a push went though or not.

> 
> > d) conveniently unpush, unrecord, and revert a patch, so that if the
> > maintainer rejects it, it's very easy for me to just ditch it in my own
> > repository, and thus sync up my local repository with the maintainer's
> > official tree
> 
> Hmmmm.  The unrecord and revert combination is handled by the unpull
> command, which just unrecords and reverts a patch.  See above for the
> unpush.

So if you have repo A and I have repo B, and I make a change to B and
push it to you, and you then reject the change; if I then unrecord and
revert, will our two repos be identical again? (assuming no extraneous
developments).

Be well,
Zack

> -- 
> David Roundy
> http://www.abridgegame.org
> 
> _______________________________________________
> darcs-users mailing list
> darcs-users at abridgegame.org
> http://www.abridgegame.org/mailman/listinfo/darcs-users

-- 
Zack Brown