This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Patch to /etc/profile to deal with $HOME with a space



> -----Original Message-----
> From: Harig, Mark 
> Sent: Tuesday, November 30, 2004 2:26 PM
> To: cygwin@cygwin.com
> Subject: RE: Patch to /etc/profile to deal with $HOME with a space
> 
> 
> 
> > > 
> > > 4. This problem could be reported to Bugzilla, with
> > >    a patch file attachment.  Please see
> > > 
> > >    http://sourceware.org/bugzilla/enter_bug.cgi?product=cygwin
> > > 
> > >    and select 'Cygwin Applications' as the Component.
> > > 
> > >    After you have entered the Summary and Description, revisit
> > >    the Bugzilla report, and click on the 'Create new attachment'
> > >    link.  It will allow you to attach a patch file, and select
> > >    that type of file.
> > 
> > Didn't we say that before?
> > Please don't file arbitrary patches to bugzilla by yourself!
> > Let the developers do that, based on the discussion here.
> > -- 
> > Reini Urban
> 
> OK.  Should this be added to http://cygwin.com/problems.html?
> 
> Or, should subscribers to this list not be referred to Bugzilla?
> 

Also, does http://cygwin.com/contrib.html need to be updated in
light of the use of Bugzilla, or is it still the preferred way to
provide patches?

From the contrib.html page:

> When you have finalized your changes
>
> Once you've finished making and testing your changes, you should send a unified diff to the cygwin-patches list. As an example, if you have modified several files in /c/src/winsup, then do the following in bash:
>
>       cd /c/src/winsup
>       cvs diff -up > /tmp/mypatch
>
> This will produce one file with all of your changes, making it easy for someone to review and apply. Send the contents of this file as plain text. Do not uuencode or otherwise encrypt it.
>
> Then send it to the cygwin-patches list in an email along with an explanation of what the change does. Make sure that you include a ChangeLog entry. If you have never used a ChangeLog before 1) refer to the GNU ChangeLog Standards and 2) model your entry after other entries in the file winsup/ChangeLog.

-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]