Databases
StackOverflow2013
Postsdbo
POrsync exclude according to .gitignore & .hgignore & svn:ignore like --filter=:C
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POrsync exclude according to .gitignore & .hgignore & svn:ignore like --filter=:C
    primarykey
    data
    text
    <p>Rsync includes a nifty option <code>--cvs-exclude</code> to “ignore files in the same way CVS does”, but CVS has been obsolete for years. Is there any way to make it also exclude files which would be ignored by modern version control systems (Git, Mercurial, Subversion)?</p> <p>For example, I have lots of Maven projects checked out from GitHub. Typically they include a <code>.gitignore</code> listing at least <code>target</code>, the default Maven build directory (which may be present at top level or in submodules). Since the contents of these directories are entirely disposable, and they can be far larger than source code, I would like to exclude them when using rsync for backups.</p> <p>Of course I can explicitly <code>--exclude=target/</code> but that will accidentally suppress unrelated directories that just happen to be named <code>target</code> and are not supposed to be ignored.</p> <p>And I could supply a complete list of absolute paths for all file names and patterns mentioned in any <code>.gitignore</code>, <code>.hgignore</code>, or <code>svn:ignore</code> property on my disk, but this would be a huge list that would have to be produced by some sort of script.</p> <p>Since rsync has no built-in support for VCS checkouts other than CVS, is there any good trick for feeding it their ignore patterns? Or some kind of callback system whereby a user script can be asked whether a given file/directory should be included or not?</p> <p><em>Update</em>: <code>--filter=':- .gitignore'</code> as suggested by LordJavac seems to work as well for Git as <code>--filter=:C</code> does for CVS, at least on the examples I have found, though it is unclear if the syntax is an exact match. <code>--filter=':- .hgignore'</code> does not work very well for Mercurial; e.g. an <code>.hgignore</code> containing a line like <code>^target$</code> (the Mercurial equivalent of Git <code>/target/</code>) is not recognized by rsync as a regular expression. And nothing seems to work for Subversion, for which you would have to parse <code>.svn/dir-prop-base</code> for a 1.6 or earlier working copy, and throw up your hands in dismay for a 1.7 or later working copy.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJesse Glick
    1. USJesse Glick
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POrsync exclude according to .gitignore & .hgignore & svn:ignore like --filter=:C
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POrsync exclude according to .gitignore & .hgignore & svn:ignore like --filter=:C
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POrsync exclude according to .gitignore & .hgignore & svn:ignore like --filter=:C
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSounds a bit like it would be a good idea to submit a patch for rsync that adds support for .gitignore, .hgignore, etc.
      singulars
      1. POrsync exclude according to .gitignore & .hgignore & svn:ignore like --filter=:C
      1. USThiefMaster
    2. CO@ThiefMaster: I filed https://bugzilla.samba.org/show_bug.cgi?id=9744 as a starting point.
      singulars
      1. POrsync exclude according to .gitignore & .hgignore & svn:ignore like --filter=:C
      1. USJesse Glick
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload