bug-fileutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: fileutils `snapshot' extension


From: Jim Meyering
Subject: Re: fileutils `snapshot' extension
Date: 27 May 2001 13:21:46 +0200
User-agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.0.104

Russell Senior <address@hidden> wrote:
| I have deployed a partially complete version of the `snapshot' program
| I described earlier in this thread.  I am interested to know if the
| fileutils maintainers are interested in this program as a contribution
| to the package.

Have you looked at rsync?

  http://samba.anu.edu.au/rsync/index.html

Although I'm not sure precisely what you're proposing,
I suspect it can already do some of what you want.

If you're still convinced your new functionality belongs in
the fileutils, please give some us some more information:

--------------
Here are some guidelines for contributing code to the fileutils,
textutils, and sh-utils packages.

Send patches. (send unified diffs, please -- i.e. diff -u format) If your
changes fix bugs, the bar is quite low in that I don't need much more
than to understand what the original problem was.  However, it helps
a lot if you can give me enough information to reproduce the problem.

On the other hand, if you're adding new features, please follow the
guidelines below:

  - convince me that this is a useful change/addition
      (if you're adding yet another option to ls, the above is pretty hard)

  - convince other people of the same thing
      One way to do that is to send mail to address@hidden
      (aka the gnu.utils.bug news group) including as much description
      and justification as you can.  Based on the feedback that generates,
      you may be able to convince me.

Once we agree the change is useful and get around to considering the
actual addition to the code, it helps if you do the following:

  - base your changes on the latest test release -- currently here:
      ftp://alpha.gnu.org/gnu/fetish/

  - follow the guidelines in the GNU Coding Standards (standards.info)
      which is distributed as part of the autoconf package.

  - include changes to the texinfo documentation, and be sure to update
      the --help output.

  - finally, if the change is `significant' you'll have to send signed
      copyright assignment papers to the FSF

And you'll have to be patient and expect delays on my part.
It is unusual that I spend more than a few hours per week
on the packages I maintain.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]