Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Git update

Thanks Chris, commenting on the bug is good. Although Denis is well
aware of our desires and wants to help us get onto git. Being in
Ottawa has its advantages :).

On Tue, Jun 29, 2010 at 3:48 PM, Chris Aniszczyk <caniszczyk@xxxxxxxxx> wrote:
> On Tue, Jun 29, 2010 at 10:48 AM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:
>> Hey gang,
>> I talked with Denis at the Helios release repository. Only the egit is
>> currently allowed to use Gerrit. It's partly a legal process issue
>> since you need to be able to generate the iplog like we can from
>> bugzilla (mind you Chris zx already has this coded up for Gerrit). The
>> bigger issue though is just the server power needed to support Gerrit
>> for more projects and that's probably the bigger issue. I'll continue
>> to work with them and see if we can be first in line when and if they
>> do decide to support it.
>
> If you want Gerrit, please state it on this bug...
>     https://bugs.eclipse.org/bugs/show_bug.cgi?id=283749
>
> The iplog shouldn't be much of an issue as the git log contains all
> the information... i.e...
>
> commit 6a4218ebd200b139c292807fe41b4d05bf9284ff
> Author:     Dariusz Luksza <dariusz@xxxxxxxxxx>
> AuthorDate: Sat Apr 17 22:35:08 2010 -0400
> Commit:     Chris Aniszczyk <caniszczyk@xxxxxxxxx>
> CommitDate: Thu Jun 17 19:09:09 2010 -0500
>
>    Add preliminary synchronization support within Eclipse for branches.
>
>    Implements synchronization participants and resource variants for
>    allowing clients to synchronize Eclipse resources against the Git
>    index and a given branch.
>
>    Synchronization can be launched for project's context menu by 'Team ->
>    Synchronize...' and from 'Repositories View' from branch context menu.
>
>    In 'Synchronize repository' dialog user can choose source and
>    destination branch (or tag). He can also define does local uncommited
>    changes should be included in 'Synchronize view'.
>
>    CQ: 4122
>    Bug: 309582
>    Also-by: Remy Suen <remysuen@xxxxxxxxxx>
>    Change-Id: Ib838a6c88eccbef8c7ffb6aa1c602bdc8778dbc6
>    Signed-off-by: Dariusz Luksza <dariusz@xxxxxxxxxx>
>    Signed-off-by: Matthias Sohn <matthias.sohn@xxxxxxx>
>    Signed-off-by: Chris Aniszczyk <caniszczyk@xxxxxxxxx>
>
> We have some consistent log messages to ensure that we know who the
> author was, who the committer was... if there was a CQ involved... if
> there was a bug involved...etc... in the end, all of our iplog
> information is generated from the git repository itself, gerrit is
> only used to help to figure out who is a committer based on committer
> ids.
>
>> But that does mean, we need to be prepared to go to git without Gerrit
>> and will need to figure out what the contribution process (i.e. what
>> would patches look like) is in that case.
>
> Gerrit shouldn't be required for you to use Git, it should be optional imho.
>
> There are many Git users who don't use Gerrit yet, although I believe
> it would be beneficial to have a large instance at Eclipse.
>
> --
> Cheers,
>
> Chris Aniszczyk
> http://aniszczyk.org
> +1 860 839 2465
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>


Back to the top