Re: Changelog and git log hygiene

Hi Ivan Ivan Vučica wrote: > > Is this a fix? Is this a security fix? Is this just a part of a > security fix? Or is this a new feature? Or is this a portion of a new > feature? Has this skeleton implementation been finished before this > release -- how do we announce the work done?

Re: Changelog and git log hygiene

I can concur it can be senseless with 1:1 mapping between commits and the logs. However neither is that true, not have the git commit messages been kept up to date, nor has there been an easily interpretable log of what changes have been made. I would propose changelog can be mutable (if you

Re: Changelog and git log hygiene

I, honestly, believe that the ChangeLog should be phased out. Either that, or the git log should be used to generate it. I, need to update the ChangeLog as I have not added a LOT of my recent changes since they have been extensive. I realize I am in the wrong here, but I can see the logic

Re: Changelog and git log hygiene

. Don't drop things just because "right now" you don't need them. Please make git commits standalone useful. Please help with news.texi file. If a section for next release doesn't exist, add it; we can fix the version more easily than adding semantic description later. I'll commit 1.27.0 sho

Changelog and git log hygiene

edits for formatting follow. Note that this looks to be a problem across the board with all committers, nobody in particular: git commit message: "Fix crash in gdomap when an invalid hostname is given for the -M option" changelog message: "* Tools/domap.c: Fix crash in donames() w

Re: Migration to Git

Hi, On 02/12/2017 22:41, Ivan Vučica wrote: But good reminder. I believe each GAP project should be separated into its own project, probably under separate GH org (“gnustep-gap”?), or when we move to a self-hosting. I will spend the time on this, if Riccardo believes we should do this.

Re: Migration to Git

On 2 December 2017 at 21:38:49, Bertrand Dekoninck ( bertrand.dekoni...@gmail.com) wrote: > This VM has also been backing up SVN of gap hourly; it will not be > doing so anymore once shut down. (I completely forgot that it's doing > so. I also never set up monitoring for this, nor did I set up

Re: Migration to Git

Hi, Le 02/12/2017 à 22:16, Ivan Vučica a écrit : Short updates: On Mon, Jun 12, 2017 at 11:14 PM Ivan Vučica > wrote: ## Is this a move to Github? No. Strong and vocal feedback of the community has been heard and Github is intended

Re: Migration to Git

Short updates: On Mon, Jun 12, 2017 at 11:14 PM Ivan Vučica wrote: > ## Is this a move to Github? > > No. > > Strong and vocal feedback of the community has been heard and Github > is intended as a temporary stop. We'll sort out a different hosting > provider, most probably

Re: Migration to Git

Thanks for the offer -- it's appreciated. At this time no help is required, just time. On Tue, Jun 20, 2017 at 9:04 PM, Matt Butch wrote: > I’d certainly be willing to help move to a self hosted GitLab instance if > that’s the direction we want to go. > >> On Jun

Re: Migration to Git

I’d certainly be willing to help move to a self hosted GitLab instance if that’s the direction we want to go. > On Jun 20, 2017, at 15:49, Ivan Vučica wrote: > > Move to gnu.org-hosted mailing list has not happened yet, and there > has not yet been work on moving primary

Re: Migration to Git

If you wish not to interact with Github through the web, you can use wget or curl to download the JSON descriptor of all our repos. You can use jq to process it further and get just the URLs to clone: for i in $(seq 1 3) ; do curl https://api.github.com/orgs/gnustep/repos?page=$i | jq -r

Re: Git migration nearly complete

That's the email address, not the username :) but I believe your username to be 'afedor' (which has appeared on many of the commits after I pushed them). If this is not the case, let me know ASAP. On Tue, Jun 13, 2017 at 4:31 AM, Adam Fedor wrote: > > On Jun 11, 2017, at 5:20

Re: Git migration nearly complete

> On Jun 11, 2017, at 5:20 PM, Ivan Vučica wrote: > > - long-standing contributors who've had commit access before should > send Gregory or me their Github username, so they can be added to the > gnustep org Hi Ivan, My GitHub account is adam.fe...@gmail.com

Re: Migration to Git

Giving the signature a second shot (it would've been valid if the email has not been wrapped to 80ch; there should be two whitespaces between signature and filename, not a newline): -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 19ea8495f9b64dd82c601cb33c4c7076a9ce61e5441e216f8544630515c72a4e

Migration to Git

Hello, The first step in migration to Git is pretty much complete. You can find the new repositories at https://github.com/gnustep/. ## What happened? Gna.org has shut down, and we have luckily had an rsynced copy of the entire Subversion history backed up. I've spent most evenings last week

Git migration nearly complete

; the directory structure and revisions will obviously be different, but Github offers a Subversion frontend to the Git repositories - note that whatever future Git hosting software we choose to use might not give you the same feature (but it's expected that we'll keep a primarily-read-mirror on Github

Re: Authors.txt file for GIT migration...

On Thu, Mar 10, 2016 at 3:52 AM, Gregory Casamento wrote: > Hey guys, > > All suggested corrections made. Please let me know if there is anything > else. Otherwise this is the final version. > > GC Moving this onto gnustep-dev@ only. I'll guess the version in the

Git migration (was Re: Authors.txt file for GIT migration...)

On Wed, Mar 09, 2016 at 10:52:42PM -0500, Gregory Casamento wrote: > All suggested corrections made. Please let me know if there is anything else. > Otherwise this is the final version. Not a comment on the Authors file, but related to the git conversion. I've done a couple of conve

Re: Authors.txt file for GIT migration...

Please don’t use my swan.ac.uk address. GitHub already knows about git...@theravensnest.org, so that’s probably the best one for use in a git repo. David > On 2 Mar 2016, at 04:30, Gregory Casamento <greg.casame...@gmail.com> wrote: > > Hey guys, > > I am us

Re: Authors.txt file for GIT migration...

Hi, Gregory Casamento wrote: Hey guys, I am using the attached file as the authors file for git migration. If any of you remember any of these handles, please add the email and name. There are a few which are not filled in. There are also about 5 IDs which are not currently identified

Re: Authors.txt file for GIT migration...

On Tue, Mar 1, 2016 at 8:30 PM, Gregory Casamento <greg.casame...@gmail.com> wrote: > Hey guys, > > I am using the attached file as the authors file for git migration. If any > of you remember any of these handles, please add the email and name. There > are a few

Re: Authors.txt file for GIT migration...

Wim == Wim (Willem Rein) Oudshoorn; xs4all.nl> --Robert > On Mar 1, 2016, at 23:30, Gregory Casamento <greg.casame...@gmail.com> wrote: > > Hey guys, > > I am using the attached file as the authors file for git migration. If any > of you remember any of these ha

Authors.txt file for GIT migration...

Hey guys, I am using the attached file as the authors file for git migration. If any of you remember any of these handles, please add the email and name. There are a few which are not filled in. There are also about 5 IDs which are not currently identified. Presumably because those people

Re: Proposal: Switch back to savannah using GIT

Ivan mentioned >> Savannah doesn't support separate repos, what does that mean to us? > > It means all GNUstep components would exist as a single Git repo, which > is plain wrong. If anything, it means you have to version and branch > everything at once (i.e. every app would have

Re: Proposal: Switch back to savannah using GIT

On 29 May 2015, at 00:27, Stefan Bidigaray stefanb...@gmail.com wrote: So, reading everyone's reply I get the impression that feel that GIT really isn't all that great if you're not using it with a more powerful host like GitHub. Is this true? I've only ever used SVN and CVS, and only

Re: Proposal: Switch back to savannah using GIT

Dne 29.5.2015 01:27, Stefan Bidigaray napsal: Sorry for being late to the discussion, yet again! I haven't committed much recently, but I still wanted to weight-in. So, reading everyone's reply I get the impression that feel that GIT really isn't all that great if you're not using

Re: Proposal: Switch back to savannah using GIT

the equivalent of a fork which is not something I'm opposed to talking about. GC On Fri, May 29, 2015 at 4:42 AM David Chisnall thera...@sucs.org wrote: On 29 May 2015, at 00:27, Stefan Bidigaray stefanb...@gmail.com wrote: So, reading everyone's reply I get the impression that feel that GIT really

Re: Proposal: Switch back to savannah using GIT

of the code in subversion. I agree with David. Where we are hosted is extremely important since it has everything to do with visibility. I don’t quite agree here. git svn does a reasonable job, with the goal of making it easy to use git to push back into an upstream svn repo. For the git repo here

Re: Proposal: Switch back to savannah using GIT

already done. The github mirror is a full mirror of all of the code in subversion. I agree with David. Where we are hosted is extremely important since it has everything to do with visibility. I don’t quite agree here. git svn does a reasonable job, with the goal of making it easy to use git

Re: Proposal: Switch back to savannah using GIT

as a single Git repo, which is plain wrong. If anything, it means you have to version and branch everything at once (i.e. every app would have to have the same version number). Savannah also looks like a resurrection from 1990s. It simply looks dead. -- Luboš Doležel

Re: Proposal: Switch back to savannah using GIT

for that is still there), so it's been around for a very long time. There's no reason it shouldn't have similar support for git added if it hasn't already been done. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo

Re: Proposal: Switch back to savannah using GIT

Dne 29.5.2015 12:46, Matt Rice napsal: I tend to side with the FSF in this regard, so I'd prefer something like gitlab which provides hosting, as well as a free software license to the software they use to host... similarly it might not be a bad idea to provide a dns alias to e.g.

Re: Proposal: Switch back to savannah using GIT

GNUstep projects, making sure that branches in svn become git branches and tags in svn become git tags. I see what you mean. I didn't use svn2git, I should look into doing that. It’s not a criticism - git svn and svn2git (which uses git svn, but also adds some stuff) are intended

Re: Proposal: Switch back to savannah using GIT

missing the steps of uploading the tarball to the destination location. With GitHub, it is two git commands to go from a working branch to a release with public tarballs available. That just leaves sending the release announcement. http://wiki.gnustep.org/index.php/Writing_Makefiles No need

Re: Proposal: Switch back to savannah using GIT

important since it has everything to do with visibility. I don’t quite agree here. git svn does a reasonable job, with the goal of making it easy to use git to push back into an upstream svn repo. For the git repo here (which I hope to have time to move back to github.com/gnustep/libobjc2

Re: Proposal: Switch back to savannah using GIT

Hi, David Chisnall wrote: - Automatic tarball generation. When I’m packaging a project for FreeBSD, it makes me very happy to learn that it’s hosted on GitHub, because if I know the release branch name or hash I can automatically generate a URL that is a tarball of the sources and tell the

Re: Proposal: Switch back to savannah using GIT

Hi, David Chisnall wrote: If what GNUstep needs is a host that most potential developers don’t have an account on (and won’t think to look at), conveys the impression that we’re a dead project, and adds more barriers to entry for new developers then, indeed, Savannah does everything that

Re: Proposal: Switch back to savannah using GIT

On Fri, May 29, 2015 at 1:55 AM, Gregory Casamento greg.casame...@gmail.com wrote: If the consensus is to move to github, then that work is basically already done. The github mirror is a full mirror of all of the code in subversion. I agree with David. Where we are hosted is extremely

Re: Proposal: Switch back to savannah using GIT

Some people can't justify hosting their sources at a 3rd party, it may not impact GNUstep as a project, but in theory one could modify the software to allow synchronizing bug reports (they may have this already I haven't looked) I wouldn't say savannah is obscure, it just (cant figure out a way

Re: Proposal: Switch back to savannah using GIT

So, something even more obscure than savannah? On Fri, May 29, 2015 at 6:46 AM Matt Rice ratm...@gmail.com wrote: On Fri, May 29, 2015 at 1:55 AM, Gregory Casamento greg.casame...@gmail.com wrote: If the consensus is to move to github, then that work is basically already done. The

Re: Proposal: Switch back to savannah using GIT

On 29 May 2015, at 13:18, Richard Frith-Macdonald richardfrithmacdon...@gmail.com wrote: Oh, and this doesn’t actually do what I do (and what is best practice to do) to ensure a clean release tarball, which is tar up the result of svn export, to ensure that the tarball exactly matches the

Re: Proposal: Switch back to savannah using GIT

On 29 May 2015, at 14:31, David Chisnall thera...@sucs.org wrote: On 29 May 2015, at 13:18, Richard Frith-Macdonald richardfrithmacdon...@gmail.com wrote: Oh, and this doesn’t actually do what I do (and what is best practice to do) to ensure a clean release tarball, which is tar up the

Re: Proposal: Switch back to savannah using GIT

tarballs from a repo. I think one issue with this is that the tags can change, see this stack overflow question on how to do this is not exactly unpopular http://stackoverflow.com/questions/8044583/how-can-i-move-a-tag-on-a-git-branch-to-a-different-commit I think it's always better to rely

Re: Proposal: Switch back to savannah using GIT

Sorry for being late to the discussion, yet again! I haven't committed much recently, but I still wanted to weight-in. So, reading everyone's reply I get the impression that feel that GIT really isn't all that great if you're not using it with a more powerful host like GitHub. Is this true

Proposal: Switch back to savannah using GIT

Hey guys, I wanted to run this past the community to see what the general feeling is. I am considering a move back to savannah utilizing git instead of subversion. The implementation of git on savannah, I believe, allows checkout and check-in VIA subversion. I would at least like to try

Re: Proposal: Switch back to savannah using GIT

Hi Greg, I don't see the big benefit in switching to git, but I wont resist that move either. We don't have that many branches of GNUstep, so cherry picking changes wont happen that often. We should make sure that the people using the only official branch, testplant, are willing to move too

Fwd: Proposal: Switch back to savannah using GIT

Forwarded to list... I forgot to add the list on this reply. -- Forwarded message - From: Gregory Casamento greg.casame...@gmail.com Date: Mon, May 25, 2015 at 8:36 AM Subject: Re: Proposal: Switch back to savannah using GIT To: Fred Kiefer fredkie...@gmx.de Hey Fred, Granted

Re: Proposal: Switch back to savannah using GIT

On Mon, May 25, 2015 at 1:40 PM, Gregory Casamento greg.casame...@gmail.com wrote: The issue with savannah at this point is that they only allow one repository per user. This is quite different from git hub which allows as many repositories as a user wants or needs. This is the only

Re: Proposal: Switch back to savannah using GIT

Nice web UIs make tracking changes easy and perhaps even enjoyable. Git ecosystem has a couple of web services that let you do that. Git would also make it easier to do code review for new developers before they make changes directly in the tree. Despite some annoying UI decisions, I'm in favor

Re: Proposal: Switch back to savannah using GIT

The issue with savannah at this point is that they only allow one repository per user. This is quite different from git hub which allows as many repositories as a user wants or needs. This is the only problem really facing us.The git repo at github contains a full history of GNUstep from

Re: Proposal: Switch back to savannah using GIT

On 25 May 2015, at 08:09, Gregory Casamento greg.casame...@gmail.com wrote: Hey guys, I wanted to run this past the community to see what the general feeling is. I am considering a move back to savannah utilizing git instead of subversion. I have no strong feelings on this. While I find

Re: Proposal: Switch back to savannah using GIT

: Proposal: Switch back to savannah using GIT To: Fred Kiefer fredkie...@gmx.de Hey Fred, Granted we don't have much to worry about in the way of multiple branches at this point. I, personally, wouldn't mind using git in GNUstep because it would allow me to create any number of experimental

Re: Proposal: Switch back to savannah using GIT

On 25 May 2015, at 13:48, Ivan Vučica i...@vucica.net wrote: On Mon, May 25, 2015 at 1:40 PM, Gregory Casamento greg.casame...@gmail.com wrote: The issue with savannah at this point is that they only allow one repository per user. This is quite different from git hub which allows as many

Re: Proposal: Switch back to savannah using GIT

Hi, (sorry for some horrid to-posting, but I do not reply 1:1 here) I'm in favor of moving back to savannah again, but not the switch to GIT. Every VCS system has its pros and cons and we can debate forever. The main point is, however, what I would borrow from OpenBSD's reasoning: do

Re: Proposal: Switch back to savannah using GIT

2015-05-25 15:26 GMT+02:00 Riccardo Mottola riccardo.mott...@libero.it: I found around some useful support for SVN: I gathered/grouped here some. They are not all my opinion, but I endorse them Let me add: 10. It is possible to use git for local working directory, while interacting

Re: Proposal: Switch back to savannah using GIT

Am 25.05.2015 um 15:26 schrieb Riccardo Mottola riccardo.mott...@libero.it: Hi, (sorry for some horrid to-posting, but I do not reply 1:1 here) I'm in favor of moving back to savannah again, but not the switch to GIT. Every VCS system has its pros and cons and we can debate forever

Re: Proposal: Switch back to savannah using GIT

(Note: This email is not an attack on Subversion. I am not a fan of Git -- in fact, I avoid it whenever I can in favor of Mercurial. And it most certainly is not personal :-) but a discussion of technical merits I think Git has for our specific use case.) On Mon, May 25, 2015 at 2:26 PM, Riccardo

Re: Proposal: Switch back to savannah using GIT

Am 25.05.2015 um 16:57 schrieb Ivan Vučica i...@vucica.net: (Note: This email is not an attack on Subversion. I am not a fan of Git -- in fact, I avoid it whenever I can in favor of Mercurial. And it most certainly is not personal :-) but a discussion of technical merits I think Git has

Re: Proposal: Switch back to savannah using GIT

to easily know what I am doing. I did very heavy divide-and-conquer bug search lately and found this invaluable: Walking through versions is simpler in Subversion because it uses sequential revision numbers (1,2,3,..); Git uses unpredictable SHA-1 hashes. Going back to date-time? no thanks if I can

Re: Proposal: Switch back to savannah using GIT

Replies are below inline... On Mon, May 25, 2015 at 9:26 AM Riccardo Mottola riccardo.mott...@libero.it wrote: Hi, (sorry for some horrid to-posting, but I do not reply 1:1 here) I'm in favor of moving back to savannah again, but not the switch to GIT. Every VCS system has its pros

Re: Proposal: Switch back to savannah using GIT

No; it won't corrupt them. It just (as expected) doesn't know how to diff them nor does it try to. The problem would be if they were massive and if they would change frequently (or sometimes more than once), which would mean the amount of data you'd need to 'git clone' would grow much more sharply

Re: Proposal: Switch back to savannah using GIT

Hi, Fred Kiefer wrote: What is the problem with binary files with git? Would our image files be affected? We have plenty of them in gui (tiff, gif, icns) and it would be great to know in advance that these wont get corrupted. no they should not corrupt. I am not so worried about images

Re: Proposal: Switch back to savannah using GIT

Am 25.05.2015 um 16:57 schrieb Ivan Vučica: You mention binary and large files -- how many binary and large files do we stash? If it's many, do we care enough to want to store them in the main repository? What is the problem with binary files with git? Would our image files be affected? We

Re: Proposal: Switch back to savannah using GIT

El lun, 25-05-2015 a las 19:37 +0200, Sebastian Reitenbach escribió: On 05/25/15 09:09, Gregory Casamento wrote: Hey guys, I wanted to run this past the community to see what the general feeling is. I am considering a move back to savannah utilizing git instead of subversion

Re: Proposal: Switch back to savannah using GIT

On 05/25/15 09:09, Gregory Casamento wrote: Hey guys, I wanted to run this past the community to see what the general feeling is. I am considering a move back to savannah utilizing git instead of subversion. The implementation of git on savannah, I believe, allows checkout and check-in VIA

Re: Proposal: Switch back to savannah using GIT

sequential revision numbers (1,2,3,..); Git uses unpredictable SHA-1 hashes.” Not at all. git uses the “Parent” commit. So you can go back in history. Just not by sequential numbers but by position in the history chain. The command ‘git bisect’ tracks that for you so you don’t have to care about

Re: Git?

Banlu Kemiyatorn wrote: Why would we want to move to Git? I don't see any much benefit by doing that. And although nobody did mention anything about moving to git, I still want to made this suggestion that we should stick with SVN forever. Anyone is against m forever is a too strong statement

Re: Git?

. GIT is, in my opinion, too complicated for small to mid sized projects to use. GIT is useful when you have a large number of contributors where you are trying to keep several different branches going and pick and choose commits from any of those branches. This is, indeed, what GIT was designed

Git?

Why would we want to move to Git? I don't see any much benefit by doing that. And although nobody did mention anything about moving to git, I still want to made this suggestion that we should stick with SVN forever. Anyone is against me? --     ..     Banlu Kemiyatorn   /.../\...\   漫画家

Re: Git?

On Mon, Jan 24, 2011 at 01:53:40AM +0700, Banlu Kemiyatorn wrote: Why would we want to move to Git? I don't see any much benefit by doing that. And although nobody did mention anything about moving to git, I still want to made this suggestion that we should stick with SVN forever. Anyone

is there a git or mercurial repository of GNUstep?

I might start looking into the GNUstep code base more closely. However, I find it really annoying having to work with svn and/or ViewVC. Does anyone maintain a public clone of the GNUstep svn repository in git or mercurial? If not, is there any old clone that one could update? Now I don't

Re: is there a git or mercurial repository of GNUstep?

Hi, You can use git-svn for that: $ git svn clone gnustep_svn_url I takes time to re-create the history in the first time, but once that is finished, you have the benefits of git. Regards, Lucas On Thu, Apr 15, 2010 at 11:54, Tim Schmielau gnus...@chmielau.orangehome.co.uk wrote: I might

Re: is there a git or mercurial repository of GNUstep?

On 15 Apr 2010, at 11:20, Lucas Schnorr wrote: You can use git-svn for that: $ git svn clone gnustep_svn_url I takes time to re-create the history in the first time, but once that is finished, you have the benefits of git. Yes. I just wanted to avoid the load this places on the gna server

Re: is there a git or mercurial repository of GNUstep?

On 15 Apr 2010, at 14:31, Andrew Ruder wrote: I have a multiple-syncs-a-day git repository of several of the GNUstep projects. I can add more if you want, but here is what I have now. The nice thing about what I have is that Jeff Teunissen took the time to do all of the mappings of svn names