Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jgit-dev] [Announce] JGit / EGit release

did you test it ?

On Tue, Oct 15, 2013 at 10:26 AM, Alex Blewitt <alex.blewitt@xxxxxxxxx> wrote:


Sent from my iPhone 5

On 14 Oct 2013, at 13:45, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:

I'll stage jgit 3.1 to maven central later today


On Mon, Oct 14, 2013 at 2:24 PM, Alex Blewitt <alex.blewitt@xxxxxxxxx> wrote:
Can someone promote the JGit bits to Maven Central? It looks like someone else has punted a copy up there under a different groupid but the latest org.eclipse one is 3.0.0 still. 



Sent from my iPhone 5

On 3 Oct 2013, at 19:22, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:

On Thu, Oct 3, 2013 at 7:39 PM, <james.moger@xxxxxxxxxxx> wrote:
And for my future happiness, _please_ don't remove the "compute
change-id" button from the commit dialog or staging view even if Gerrit
is not configured for a repo.  I have been using that function without
Gerrit and losing it would be a real bummer.
didn't consider that, what are you using the ID for if you don't use Gerrit ?
One missing feature in Gitblit is a way to make a contribution to a repository.  There are two popular designs for this: the Pull/Merge Request and the Patchset.  While both have their merits, I think the Patchset approach is better for collaboration and yields a cleaner repository history.
For the past few months I have been working on a Ticket (issue/change/your favorite noun) feature for Gitblit which uses a simplified version of Gerrit's patchset mechanism (change-id: and refs/changes/..).  Because of this, right now, the "compute change-id" buttons are absolutely critical functions for me.
Secondary to me, right now, are the missing "Fetch/Push from Gerrit" menu items which is what prompted my inquiry.  The changes you've made in hiding Gerrit functionality from non-Gerrit-tagged repositories makes sense.  I'm probably the only person out there (at least for now) who is using those functions without using Gerrit as the backend.

when Gitblit supports the same way to work with patchsets we could
consider to generalize the current Gerrit support in EGit to make it work
with both systems.


Back to the top