[darcs-devel] How we handle the screened repo

Ganesh Sittampalam ganesh at earth.li
Thu Nov 22 18:13:32 UTC 2018


On 22/11/2018 09:49, Ben Franksen wrote:

> The screened repo would serve its purpose better, at least for my
> personal working style, if I could obliterate patches there if they turn
> out to be bogus or aren't accepted for other reasons. This doesn't
> happen very often but every once in a while. That doesn't mean
> contributors (me included) should push without testing or making sure
> the patch is clean etc. But we all make mistakes and sometimes
> obliterate is really just what you want to do.
> 
> We can also changes the rules back and forbid obliterate in the unlikely
> case we attract more developers in the future...

I'm fine with making this change. I think a bit of documentation on the
wiki might need to be updated and the screened mirror on hub.darcs.net
removed.

It might also help me if there was a single easy way to check if a patch
has been obliterated or I've just screwed up something, as sometimes I
don't pay much attention for a while then have to bring my local
repositories up to date. But I can't think of a trivial way to do this
so let's just see how it goes initially and tweak it if it's causing me
or anyone else significant problems in practice.

>> I don't feel too strongly either way. Changing state in a shared repo
>> introduces some overhead for users of that repo, but as you say there
>> aren't that many of us.
> 
> One way to reduce that overhead, something I have often wished for
> actually, is a darcs command that gives a comprehensive summary of the
> status of a repo with respect to its defaultrepo. Something roughly
> equivalent to
> 
>   darcs whatsnew -l; darcs push --dry-run; darcs pull --dry-run
> 
> except that the push/pull information should be a bit more concise,
> perhaps giving only the number of patches to push/pull by default. (This
> is assuming the repo has a defaultrepo set at all.)
> 
> We do have 'darcs status' as an alias for 'whatsnew -l' and one way to
> go would be turn this into a real command with these extra features.

I think this would be a reasonable command for darcs to have. I do have
my own specialised scripts for looking at some of this specifically in
the context of the darcs repos
(https://hub.darcs.net/ganesh/darcs-roundup-watch), but what you suggest
seems like quite a generally applicable concept.

Cheers,

Ganesh


More information about the darcs-devel mailing list