File: control

package info (click to toggle)
commit-patch 2.6.2-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 172 kB
  • sloc: perl: 225; sh: 141; lisp: 141; makefile: 49
file content (27 lines) | stat: -rw-r--r-- 1,252 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
Source: commit-patch
Section: vcs
Priority: optional
Maintainer: David Caldwell <david@porkrind.org>
Build-Depends: debhelper-compat (= 13), dh-elpa (>= 2.0.8~), perl
Standards-Version: 4.5.1
Homepage: https://porkrind.org/commit-patch/
Vcs-Git: https://github.com/caldwell/commit-patch.git -b debian
Vcs-Browser: https://github.com/caldwell/commit-patch/tree/debian

Package: commit-patch
Architecture: all
Depends: ${misc:Depends}, ${perl:Depends}, libipc-run-perl, patch, patchutils, emacsen-common (>= 2.0.8)
Suggests: darcs | git | mercurial | bzr | monotone | subversion | cvs
Description: utility to commit fine grained patches to source code control repositories
 Normally version control systems don't allow fine grained
 commits. commit-patch allows the user to control exactly what gets
 committed by letting the user supply a patch to be committed rather than
 using the files in the current working directory.
 .
 commit-patch supports Darcs, Git, Mercurial, Bazaar, Monotone, Subversion,
 or CVS repositories.
 .
 Also included is an Emacs interface to commit-patch. It allows you to just
 hit C-c C-c in any patch buffer to apply and commit only the changes
 indicated by the patch, regardless of the changes in your working
 directory.