Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
patch-tag-users
Home
+ new post
About this group
Join this group
Message from discussion Obliterate via web interface
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Ashley Moran  
View profile  
 More options Mar 17 2009, 5:48 pm
From: Ashley Moran <ashley.mo...@patchspace.co.uk>
Date: Tue, 17 Mar 2009 21:48:21 +0000
Local: Tues, Mar 17 2009 5:48 pm
Subject: Re: Obliterate via web interface
Print | View thread | Show original | Report this message | Find messages by this author

On 16 Mar 2009, at 15:31, Matthew Elder wrote:

> As Thomas says, the Darcs documentation strongly discourages that  
> you do an obliteration on a shared repository. All the work that  
> goes into having to notify people to obliterate it locally is one  
> pain.

Well, that was why I thought sending email notifications would be  
handy ;)

> And suppose that someone doesn't get the notification to do this and  
> pushes some new changes, the patch you just obliterated will show  
> its ugly face again.

True, but I would imagine this only being used after a very short  
time.  IE it's an emergency rescue operation.

There's another valid use for this - continuous integration.  Say I  
set up two repositories - "project" and "project-unstable".  Then I  
set up a server to continuously poll the project-unstable repo, and  
run all automated tests every time a new patch is detected.  If that  
patch is successful it could be pushed to the stable project repo,  
ready for pulling.  If it causes failures I'd love to be able to  
obliterate it on the server and have the pushing user notified.

This CI application of obliterate would be a KILLER feature for me, as  
I'm completely obsessed with automated testing*, and anything that  
helps keep code deployable is a huge win for me.

> Overall I think that the idea of obliteration doesn't fit into the  
> use case for a shared repository. Darcs rollback is the only sane  
> way to do this. I know your history won't be as neat, but obliterate  
> is a tool that is really only practical for a single author to  
> single repo relationship -- AND before they share any of these  
> changes..

I see your perspective on this.  And in general, I agree.  However, I  
think there's a use for obliterate buried in there somewhere.

> I do like Thomases idea of being able to "revirginize" the  
> repository without losing your metadata -- but again, this is in a  
> different vein than the original obliterate idea. We really need to  
> add some faqs and documentation about best practices :)

Yes, I think this could be useful too.

> Thank you for the feedback and please continue to keep us in the  
> loop as you experience issues :)

Don't worry, I'm an opinionated and vociferous user, I hope you can  
put up with me =)

Ashley

* it's how I earn my living...

--
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google