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
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
|
Logcheck - git
The logcheck git repository is available via for online browsing:
<https://salsa.debian.org/debian/logcheck>
To obtain the source, you clone it:
git clone https://salsa.debian.org/debian/logcheck.git
To submit patches, please follow this document:
<http://repo.or.cz/w/git.git?a=blob;f=Documentation/SubmittingPatches;hb=HEAD>
And send your patches via email to the Debian BTS:
<https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=logcheck>
First, the setup, which you only have to do once on each machine you work
with:
# leave out --global if you want to set your identity only for logcheck
git config --global user.name 'your name'
git config --global user.email 'your@email.address'
# the next two are not needed but ensure that git does not send patches to
# your own email address.
git config sendemail.signedoffcc false
git config sendemail.suppressfrom true
git clone https://salsa.debian.org/debian/logcheck.git
To prepare the actual patch, do the following:
git pull
git checkout -b some-name-identifying-my-work
while not finished:
// if resuming after a while, maybe update your branch:
git rebase master
// edit files
git add files
git commit
...
end
After you've brought your change to a state where you want to submit it,
please squash it into logical single commits. If you only made one change,
then this will do:
git checkout -b temp-squash master
git merge --squash some-name-identifying-my-work
git commit // ... remove the "Squashed commit of the following:" leader
git format-patch -M -s master
// now inspect the files this created in $PWD
// check that it's okay and send the patch to Debian BTS
For multiple logical changes, cherry-pick or squash-merge every commit
belonging to a change to the integration branch and then commit it.
Also, read the git-send-email manpage in case you're submitting multiple
logical changes, in case you want to thread them.
The manpage also includes information about adding a prologue message
explaining your patch, or how to insert it into an existing thread
(in-reply-to).
Developers with write access to the repository may also push their
changes, using the ssh transport instead of the git protocol.
|
