[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#789243: RFS: git-up (WAS: Bug#789243: git-up -- fetch and rebase all locally-tracked remote Git branches)



Agreed. Should I close the ITP then?

Best,
James

On 09/07/2016 1:38 AM, Christian Hofstaedtler wrote:
> * James Lu <bitflip3@gmail.com> [160709 08:37]:
>> Many few months ago, me and David prepared an upload of git-up 0.5.12-1,
>> which can be found in the Debian Ruby Git repository at
>> https://anonscm.debian.org/cgit/pkg-ruby-extras/git-up.git
> [..]
>> Upstream has not done anything so far to fix the bugs with Git 2.5
>> worktrees: https://github.com/aanand/git-up/pull/100. I'm wondering if
>> this is worth including as a patch until it is merged upstream.
> 
> Note that upstream now says:
> 
> | This project is no longer maintained, for several reasons:
> | 
> | * I've stopped using the workflow that made it relevant to me.
> | * Git 2.0 updated the default behaviour to remove the main problem it
> | was solving (by changing the default behaviour of git push so it
> | acts only on the current branch, instead of all branches).
> | * Auto-stashing is now supported natively with git rebase --autostash.
> 
> Therefore I'd strongly suggest not uploading this when it's upstream
> is already gone.
> 
> Best,
> 

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: