Hi Tim - There are lots of options depending on your familiarity with git. If you were a registered PDL developer, you would make your edits, commit, and push. If you were very familiar with git, you would make your edits, commit, and tell us where we could pull your changes (i.e. you'd make a pull request). However, as you are not familiar with git, here is what I suggest you do:
1. Make your edits, save the files. Do *not* commit via git. 2. git diff > fix-pointers.patch 3. Attach the patch to an email. One of the porters will apply it in your name. Preferably these sorts of communications would be sent to [email protected], but that's not a strong preference. We'll take patches however we can get them. :-) David P.S. Aren't you one of the Chicago Perlmongers? On Thu, Nov 10, 2011 at 2:04 AM, Tim Haines <[email protected]>wrote: > Greetings, all. > > This bug report is some general cleanup of several printf format flags. > Currently, pointer values are being printed out like this > > int *i; > printf("0x%x",i); > > which generates a warning since %x wants an unsigned int instead of a > pointer. I propose changing this to > > int *i; > printf("%p",(void*)i); > > As best I can tell, the %p flag is ANSI compliant. Does anyone have any > objection to using it? > > Since this bug fix affects several files and I don't have any experience > using Git, is there a tutorial somewhere that outlines your preferred > method of doing a check-in of multiple files and their associated comments? > I used `git clone git://pdl.git.sourceforge.net/gitroot/pdl/pdl my_dir` > to fetch the latest repository. > > Thanks. > > - Tim > > _______________________________________________ > Perldl mailing list > [email protected] > http://mailman.jach.hawaii.edu/mailman/listinfo/perldl > >
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
