On 11/03/2014 02:29 AM, Armin K. wrote:
> On 11/03/2014 12:35 AM, Bruce Dubbs wrote:
>> Armin K. wrote:
>>> Hello everyone.
>>>
>>> I was thinking about moving LFS systemd to a git repository on github,
>>> but first wanted to notify the list.
>>>
>>> Given that I'm the only contributor at the moment, with Chris jumping in
>>> to help on some occassions, I find it easier to use git than svn,
>>> especially for managing a big number of small patches and doing merges
>>> (which I won't be able since I'll be moving only the systemd branch).
>>>
>>> Does anyone object on that? I know it would be a downside that a more or
>>> less official project is being hosted somewhere else, but I don't recall
>>> that LFS server hosts any git repositories, so github is my best bet.
>>>
>>> In case nobody objects, current editors can either send me their public
>>> ssh key for commit access or send pull requests or git formatted patches
>>> (the latter two apply for everyone else).
>>
>> I don't have any significant objections, but question the need in this
>> case. First of all you are the only one making changes to the systemd
>> book. Secondly, there are only a very few packages that are different
>> between trunk and systemd. Lets look:
>>
>> Chapter 5 is identical AFAICT.
>>
>> In Chapter 6 the differences are:
>>
>> lfs has sysvinit and eudev.
>> systemd has dbus and systemd.
>>
>> The util-linux page in Chapter 6 has an option
>> --with{,out}-systemdsystemunitdir and --without-systemd
>>
>> Did I miss any differences?
>>
>
> There should be a bit more. Namely text differences in findutils and
> coreutils in order not to mention bootscripts, glibc differences
> regarding timezone symlink creation and nscd systemd integration and
> maybe one or two more.
>
>> Of course there are text differences in Chapter 7 and 8
>>
>> By transitioning, you remove the capability to browse both versions in
>> Trac and the ability to match specific commits to tickets.
>>
>> The commits won't automatically be sent to lfs-book for others to review.
>>
>> Overall it's an open source project and you are free to clone it as you
>> see fit, but I think it would be better in this case to leave things as
>> they are.
>>
>> -- Bruce
>
> Right. These are all valid points to take into consideration. But still,
> github has a very nice commit browser so you wouldn't need use trac to
> browse source. You can always do (and even need now with svn) to do a
> manual diff to spot the differences - which is what I do to find out if
> I missed anything during the merge.
>
> But, the issue with matching tickets to commits and mails are valid. I
> hardly ever have tickets for systemd branch as most of the stuff that
> has tickets is shared. I only have to handle dbus and systemd, but I
> don't even bother creating the tickets for that. I am not sure if mails
> could be sent from github to the mailing list regarding the commits. As
> I've mentioned above, there's a very nice commit browser, but not
> helpful if anyone's to comment on a specific commit via mail.
>
>
> As you can see, I can set up git repository to deliver a mail after git push, but it's not a mail one would expect. It doesn't send a "patch like" mail like svn does, but just a basic info with a direct link to the git commit that can be seen on the blfs-book. Oh, and I've disabled the email hook for BLFS branch, it was just used for testing. -- Note: My last name is not Krejzi.
signature.asc
Description: OpenPGP digital signature
-- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
