IRCloggy #git 2016-10-20

Logs Search ←Prev date Next date→ Channels Documentation

Provider of IRC logs since 2005.
WARNING: As Freenode became unjoinable and lost all warnings in topics, we cannot log channels on Freenode anymore.

2016-10-20

alex1a joined00:00
dsdeiz_ joined00:04
Dohplay joined00:04
dsdeiz left00:04
buddyq osse, it's working... only kink is that git fetch to github from my hosts ask for a password. I thought the ssh key was to bypass that.00:05
dreiss left00:07
jimi_ joined00:08
boombatower left00:08
Coka joined00:09
mischat joined00:09
Coka left00:10
nettoweb joined00:11
hahuang65 left00:12
hahuang65 joined00:12
alex1a left00:13
star_prone joined00:13
mischat left00:14
peey joined00:15
CussBot left00:16
peey I created a subdirectory within my git repo and did a git init in that directory and pushed the subdirectory to remote. I then pushed the changes to original repo to the remote, but when I try to clone it it gives me No submodule mapping found in .gitmodules for path 'new'. What should I do?00:17
star_prone left00:18
unbalancedparen joined00:18
dyek left00:19
Rodya_ joined00:20
nettoweb left00:22
crayon left00:22
alex1a joined00:22
denimsoft joined00:24
barteks2x left00:26
KnownSyntax left00:27
nitric left00:27
CussBot joined00:27
KnownSyntax joined00:28
LeBlaaanc left00:31
jstein_ joined00:31
jsteinGuest2150100:31
zivester joined00:33
jstein_jstein00:33
Derperperd joined00:33
peey left00:33
nettoweb joined00:34
e14 joined00:34
Guest21501 left00:35
denimsoft left00:38
nettoweb left00:39
kulelu88 joined00:40
BPL Any cmake contributor over here?00:40
jstein left00:40
hahuang65 left00:40
hahuang65 joined00:41
dsantiago left00:41
lagothrix joined00:43
anonymuse joined00:45
publio left00:45
cagedwisdom left00:47
parsnip0parsnip00:48
thebope joined00:48
Goplat joined00:51
einnjo joined00:53
thebope left00:53
evanwang joined00:55
e14 left00:56
_cyril_ left00:57
fstd_ joined00:58
fstd left00:58
axisys left00:58
Gsham_ left00:59
fstd_fstd00:59
CussBot_ joined00:59
CussBotGuest2809500:59
CussBot_CussBot00:59
Guest28095 left00:59
HoierM left01:00
pks left01:02
pks joined01:03
sunri5e left01:03
Jameser joined01:04
dreiss joined01:05
sunri5e joined01:06
ochorocho__ joined01:07
einnjo left01:08
parsnip left01:09
mischat joined01:10
d^sh left01:11
dreiss left01:11
d^sh joined01:11
evanwang left01:11
ochorocho__ left01:12
Motoko joined01:12
al-damiri joined01:12
krs93 joined01:13
plos left01:13
ResidentBiscuit left01:14
hahuang65 left01:14
skunkz left01:14
mischat left01:15
krs93 left01:17
krs93 joined01:17
littleforest left01:18
svm_invictvs left01:20
CussBot left01:20
Dougie187 joined01:21
CussBot_ joined01:21
CussBot_CussBot01:21
plos joined01:21
Sasazuka__ left01:25
parsnip joined01:26
axisys joined01:26
CussBot left01:26
plos left01:26
CussBot joined01:26
Dougie187 left01:28
finalbeta joined01:29
fxer left01:33
tvw left01:34
plos joined01:34
jimi_ left01:39
Skryll left01:39
plos left01:39
harish_ left01:39
ResidentBiscuit joined01:39
EvilPenguin left01:42
brokensyntax left01:44
ResidentBiscuit left01:46
brokensyntax joined01:47
drbean left01:47
drmt left01:49
thebope joined01:49
drbean joined01:50
buddyq left01:50
modlin left01:52
aspiers left01:53
Vampire0_ joined01:53
liuzhen joined01:54
thebope left01:54
Jameser left01:55
Limes_ joined01:55
BPL left01:55
BPL joined01:56
Vampire0 left01:57
BPL left01:57
pks left02:00
pks joined02:02
Rodya_ left02:02
sunri5e left02:02
kyan left02:03
sunri5e joined02:04
Jameser joined02:06
aspiers joined02:06
msonntag left02:06
Wulf joined02:07
msonntag joined02:07
plos joined02:10
star_prone joined02:13
jstimm joined02:13
Limes_ left02:14
kyan joined02:15
star_prone left02:17
flavius left02:18
Rodya_ joined02:20
svm_invictvs joined02:22
Rodya_ left02:23
Rodya_ joined02:24
hexagoxel left02:24
xshuiniu left02:24
alex1a left02:24
Jameser left02:24
safe joined02:25
SwiftMatt left02:25
plos left02:26
hexagoxel joined02:26
shakalaka left02:26
fahadash left02:26
yohnnyjoe left02:26
svm_invictvs left02:27
shakalaka joined02:28
a3Dman left02:28
Anja left02:30
Dougie187 joined02:33
a3Dman_ joined02:38
Gsham joined02:39
Gsham left02:39
krs93 left02:40
Dougie187 left02:40
Gsham joined02:40
whitby left02:40
evanwang joined02:42
Motoko left02:42
Anja joined02:43
dsdeiz_ left02:43
dsdeiz joined02:43
fedepad joined02:43
govg left02:44
xall joined02:44
chachasmooth left02:45
dsantiago joined02:46
fedepad left02:48
howdoi joined02:48
chachasmooth joined02:49
sangy left02:49
lagothri1 joined02:50
thebope joined02:50
Gsham left02:52
chartractegg joined02:52
Gsham joined02:53
lagothrix left02:53
neunon left02:55
thebope left02:55
brokensyntax left02:55
Wulf4 joined02:56
brokensyntax joined02:56
unbalancedparen left02:57
littleforest joined02:57
mangolisk joined02:59
Wulf left02:59
Wulf4Wulf02:59
Gsham left03:00
hashpuppy left03:01
xshuiniu joined03:01
ResidentBiscuit joined03:02
blackwind_123 left03:02
harish_ joined03:02
dsantiago left03:03
aavrug joined03:03
blackwind_123 joined03:03
xall left03:04
dviola left03:04
e14 joined03:06
brokensyntax left03:06
brokensyntax joined03:07
anonymuse left03:08
e14 left03:08
e14 joined03:09
chartrac_ joined03:09
chartractegg left03:10
mischat joined03:12
gasull joined03:14
Vortex35 joined03:14
nettoweb joined03:14
gasull left03:14
buddyq joined03:15
nettoweb left03:15
Vortex34 left03:16
mischat left03:17
Andrew_K joined03:18
justrohu joined03:20
chartractegg joined03:21
chartrac_ left03:21
govg joined03:23
fahadash joined03:24
skyfaller left03:25
alex1a joined03:26
mountpoint left03:27
rchavik joined03:28
AndreSomers joined03:28
littleforest left03:28
e14 left03:29
boombatower joined03:31
al-damiri left03:32
neunon joined03:36
brokensyntax left03:38
krs93 joined03:40
brokensyntax joined03:41
durham left03:41
PioneerAxon left03:41
PioneerAxon joined03:42
demo joined03:42
xall joined03:43
tax left03:45
arescorpio left03:45
parsnip demo: hi03:47
thebope joined03:51
safe left03:51
dreiss joined03:52
mehola joined03:54
a_thakur joined03:54
thebope left03:55
govg left03:55
mizu_no_oto joined03:57
kyan left03:58
kulelu88 left04:00
ResidentBiscuit left04:01
Motoko joined04:03
tjone270 left04:03
Rodya_ left04:06
shaggycat joined04:07
peterR`` joined04:08
Rodya_ joined04:10
lindenle left04:10
LeBlaaanc joined04:11
thiago joined04:12
LeBlaaanc left04:12
mischat joined04:13
demo left04:14
Rodya_ left04:14
mischat left04:17
Rodya_ joined04:20
chartractegg left04:21
foist left04:23
svm_invictvs joined04:24
zivester left04:24
liuzhen left04:25
cagedwisdom joined04:25
eshlox joined04:25
littleforest joined04:25
SpeakerToMeat left04:27
chartractegg joined04:28
dreiss left04:30
Anja left04:31
Anja joined04:31
xameada left04:32
chartractegg left04:34
Cabanossi left04:35
Cabanossi joined04:37
rafalcpp_ left04:39
ToBeCloud joined04:41
gitinfo set mode: +v04:41
mycelium joined04:43
aidalgol left04:44
svm_invictvs left04:44
daey_ joined04:45
romerocesar left04:46
daey left04:48
daey_daey04:48
brillenfux joined04:51
thebope joined04:52
phanimahesh joined04:52
xameada joined04:52
dsantiago joined04:54
parsnip left04:54
Ryanar left04:55
thebope left04:56
Rodya_ left04:57
dermoth left05:00
dermoth joined05:00
ayogi joined05:01
mizu_no_oto left05:01
msonntag left05:01
sea-gull joined05:01
GT4066 joined05:01
govg joined05:02
frobnic left05:02
msonntag joined05:02
frobnic joined05:04
shaggycat left05:05
romerocesar joined05:05
sdothum left05:06
bmahe joined05:09
svm_invictvs joined05:10
lindenle joined05:11
anotheryou_ joined05:13
shaggycat joined05:13
mischat joined05:14
lindenle left05:15
hahuang65 joined05:17
anotheryou_ left05:18
mischat left05:19
dan2k3k4 joined05:22
mycelium left05:26
fahadash left05:26
CEnnis91 left05:28
_geoff joined05:31
Karunamon left05:32
boombatower left05:32
Karunamon joined05:32
parsnip joined05:34
BanaShip3hs joined05:36
BanaShip3hs left05:37
Anja left05:39
romerocesar left05:39
Karunamon left05:40
Karunamon joined05:41
bongjovi left05:44
zeroed joined05:45
Karunamon left05:46
spb joined05:46
diogenese joined05:46
Karunamon joined05:46
robogoat joined05:46
diogenese left05:47
brokensyntax left05:47
_geoff left05:48
bluezone left05:48
theskillwithin left05:49
brokensyntax joined05:49
qt-x joined05:49
mure joined05:49
brokensyntax left05:50
dreiss joined05:50
brokensyntax joined05:50
mure left05:50
Murii joined05:51
ThomasLocke joined05:52
Karunamon left05:52
me_and joined05:52
thebope joined05:53
diogenese joined05:54
kaldoran joined05:54
liuzhen joined05:55
Dohplay left05:55
Anja joined05:55
Raging_Hog joined05:57
thebope left05:57
jaguarmagenta joined06:00
LeBlaaanc joined06:01
LucaTM joined06:03
jaguarmagenta left06:03
LeBlaaanc left06:03
Repox joined06:04
Karunamon joined06:04
nidr0x left06:04
cdown joined06:04
jaguarmagenta joined06:04
subhojit777 joined06:04
jaguarmagenta left06:05
jaguarmagenta joined06:05
ahmedelgabri joined06:08
lb1c joined06:08
jaguarmagenta left06:09
jaguarma_ joined06:09
ahmedelgabri left06:09
cdown_ joined06:09
fedepad joined06:09
ahmedelgabri joined06:09
rendar joined06:10
jaguarma_ left06:10
Rhonda joined06:10
liuzhen left06:10
harish_ left06:10
qt-x left06:11
rscata joined06:11
cdown left06:12
cdown_cdown06:12
chele joined06:12
gniourf left06:13
qt-x joined06:13
raspado left06:14
gniourf joined06:14
liuzhen joined06:14
raspado joined06:14
mischat joined06:15
roelmonnens joined06:18
raspado left06:19
aidalgol joined06:20
jnavila joined06:21
JeroenT joined06:22
cdown left06:24
mischat left06:24
littleforest left06:25
cdown joined06:26
cdown left06:26
b100s left06:26
cdown joined06:28
buddyq left06:29
ahmedelgabri left06:30
zulutango joined06:32
freimatz joined06:32
CheckDavid left06:33
pitastrudl hello06:33
govg left06:33
pitastrudl should i have my gitignore file synced in the repo?06:33
madewokherd left06:34
drbean left06:34
bocaneri joined06:38
cagedwisdom left06:38
kadoban pitastrudl: Usually, yeah.06:38
Wulf left06:38
Wulf joined06:38
bruce_lee joined06:39
bruce_lee left06:39
bruce_lee joined06:39
pitastrudl i was wondering how LF and CLRF work, i get the warning "LF will be replaced by CRLF in git "06:39
like will windows/unix care or will it become unreadable by either06:39
cyan__ joined06:39
bocaneri left06:40
bmahe left06:41
bocaneri joined06:41
bmahe joined06:42
star_prone joined06:42
gtristan joined06:43
djb-irc left06:44
tyreld left06:45
star_prone left06:45
star_prone joined06:45
hahuang65 left06:45
ISmithers1 joined06:46
ISmithers left06:46
brokensyntax left06:46
cdown_ joined06:46
elect joined06:47
brokensyntax joined06:47
cdown left06:48
qpdb joined06:50
corsibu joined06:50
ToBeCloud left06:50
cagedwisdom joined06:51
cdown joined06:51
cdown_ left06:51
fees joined06:52
cdown_ joined06:53
thebope joined06:53
cdown left06:56
cdown_cdown06:56
overlord_tm joined06:57
OCram85 joined06:57
thebope left06:58
johnny56 left06:58
xall left06:58
ISmithers1 left06:58
sea-gull left06:58
todd_dsm left07:00
JeroenT_ joined07:01
JeroenT left07:03
xall joined07:03
alphor left07:04
albel727 left07:04
shirty joined07:06
TomyWork joined07:07
alphor joined07:07
WayToDoor joined07:07
hariel left07:07
Jameser joined07:08
lordjancso joined07:09
liuzhen left07:09
dreiss left07:10
liuzhen joined07:10
drbean joined07:11
eduardas_m joined07:12
harish_ joined07:12
bmahe left07:14
cdown_ joined07:15
vuoto joined07:16
cdown left07:18
cdown joined07:20
cdown_ left07:21
_ikke_ pitastrudl: Depends on the program07:22
pitastrudl: On linux, crlf might show up as two new lines07:22
lf might not show as new line in windows at all (in notepad for example)07:23
qpdb left07:23
pitastrudl i see07:23
Motoko left07:24
pitastrudl will have to find a way on how to go about it i guess07:24
im getting that warning when im trying to sync the gitignore file07:24
i edited it in vim, on git bash in windows07:24
osse pitastrudl: what does 'file .gitignore' say ?07:24
matthiaskrgr_matthiaskrgr07:25
pitastrudl ASCII text07:25
osse that's it?07:25
pitastrudl thats it07:25
Haliucinas joined07:25
osse hmm, open it in vim. what's does ':set ff?' say?07:26
pitastrudl osse do i know u from somewhere, i feel like i've seen u on another irc channel07:26
fileformat=unix07:26
osse pitastrudl: what does 'git show HEAD:.gitignore | file -' say?07:27
ahmedelgabri joined07:27
pitastrudl fatal: Path '.gitignore' exists on disk, but not in 'HEAD'.07:27
/dev/stdin: no read permission07:27
jnewt left07:27
pitastrudl huh07:27
Balliad joined07:28
elastix joined07:28
osse oh it's a new file?07:29
i'd commit it and then re-run that command07:29
cdown left07:29
pitastrudl ok07:29
osse I have a feeling some of git's warning messages say "foo will be replaced by bar" when it should've been the other way around.07:29
pitastrudl git show HEAD:.gitignore | file -07:30
/dev/stdin: ASCII text07:30
osse or maybe repo settings mean it should be crlf and git is confused07:30
ok, good.07:30
pitastrudl why does it matter if its in ascii?07:30
osse now remove the file. then git checkout HEAD -- .gitignore07:30
cdown joined07:30
osse It doesn't. in this case file will print either "ASCII text" or "ASCII text with CRLF terminators".07:31
systemovich joined07:31
jnewt joined07:31
pitastrudl oh wait07:31
remove it from where?07:31
osse disk07:31
rm .gitignore07:31
cdown left07:31
osse so that git recreates it07:31
krs93 left07:31
pitastrudl oh, forgot to do that before i used "git checkout HEAD -- .gitignore"07:31
so i should git reset?07:31
osse it's fine07:31
rm and do it again07:32
eka joined07:32
buddyq joined07:32
cdown joined07:32
mangolisk left07:33
pitastrudl ok i deleted the gitignore, and now?07:33
how do i pull it back?07:33
osse git checkout HEAD -- .gitignore07:33
pitastrudl ohh07:34
what did that line do?07:34
johnny56 joined07:34
osse as you put it, it "pulled it back"07:34
pitastrudl well now it's ".gitignore: ASCII text, with CRLF line terminators"07:34
so that's good i guess07:34
osse aka. get it from HEAD and put in disk07:34
pitastrudl cool07:34
osse everything is good i think07:35
\o/07:35
pitastrudl wooo07:35
:D07:35
thank you07:35
grift left07:35
osse now gimme a karambit07:36
pitastrudl nuuuuuuh07:36
muh pixels07:36
buddyq left07:37
encod3 joined07:37
maret joined07:37
star_prone left07:38
grift joined07:38
cizra joined07:39
Wulf left07:41
GavinMagnus joined07:42
cizra Hello! I used git filter-branch --subdirectory-filter to split out a subdirectory into a new repo. However, after cloning the filtered repo to a new one, it's still big. I used the one-liner solution (answer #2) from http://stackoverflow.com/questions/10622179/how-to-find-identify-large-files-commits-in-git-history to find large objects -- indeed, I do have binary junk in the history. How do I 1) figure out07:43
how my repo references it (these objects are not visible in "git log") and 2) get rid of them?07:44
encod3 left07:45
OCram85 left07:45
encod3 joined07:46
moop left07:47
King_Hual joined07:47
moop joined07:48
Alienpruts joined07:49
qpdb joined07:50
Endarked joined07:50
grayjoc joined07:50
brk_ joined07:51
_ADN_ left07:52
flaviodesousa joined07:53
dan2k3k4 left07:53
ahmedelgabri left07:54
phanimahesh left07:54
thebope joined07:54
ahmedelgabri joined07:54
ahmedelgabri left07:55
djb-irc joined07:55
anuxivm joined07:56
brokensyntax left07:56
hfr joined07:57
xall left07:57
brokensyntax joined07:57
davimore_ joined07:58
rominronin joined07:58
anuxivm left07:58
aswen joined07:58
thebope left07:59
Pieplay joined07:59
kurkale6ka joined07:59
acetakwas joined07:59
davimore__ joined07:59
davimore left08:01
jknetl joined08:02
luke_penn joined08:02
rominronin left08:02
davimore_ left08:03
rominronin joined08:03
djb-irc left08:03
ahmedelgabri joined08:06
hfr left08:06
Goplat left08:06
tlaxkit joined08:07
lus left08:07
JeroenT_ left08:08
Limes_ joined08:08
Ravana left08:09
jfr joined08:10
mikecmpbll joined08:10
mischat joined08:10
corsibu left08:11
corsibu joined08:11
nd joined08:12
dan2k3k4 joined08:12
_ADN_ joined08:13
JeroenT joined08:13
qws-user-1229 left08:13
JeroenT left08:14
JeroenT joined08:14
ki0 joined08:14
govg joined08:15
qws-user-1228 joined08:15
mischat left08:15
djb-irc joined08:15
nd_ left08:16
corsibu left08:16
a_thakur left08:18
cdown left08:19
Murii left08:20
cdown joined08:20
jnewt left08:20
halbomin joined08:20
star_prone joined08:22
JeroenT left08:24
JeroenT joined08:24
sveinse joined08:24
lss8 joined08:25
sveinse Mercurial has a function to show incoming commits upstream without fetching/pulling (hg incoming). Is there an git equivalent of that?08:25
kadoban sveinse: Not without fetching, no08:26
freimatz left08:26
corsibu joined08:26
kadoban You could check that what you have is not the same as the remote, but that's all you can really see without fetching.08:26
vuoto left08:27
barteks2x joined08:27
ayjay_t left08:27
ayjay_t joined08:27
marcogmonteiro joined08:28
sveinse all right. this is on a bare mirror, can I then clone the mirror, fetch from (the first) origin and diff them somehow to show what has changed?08:29
elastix left08:29
WayToDoor left08:29
tvw joined08:29
kadoban sveinse: I don't understand I don't think. You should be able to just fetch and then check what's different if you like? Must be missing something.08:30
acetakwas left08:32
brokensyntax left08:32
sveinse kadoban: We have a local bare mirror in house of an upstream repo, because we make medical validated SW and it must be controlled. So before I pull in an update from upstream, I need to know in advance what has changed (in any branch) before I can get the authorization to fetch the update.08:32
buddyq joined08:33
Serpent7776 joined08:34
\du joined08:34
\du left08:34
\du joined08:34
kadoban You can't even fetch without authorization of some kind? That sounds rather terrible. So you can do anything except mess with your "local bare mirror", I assume, right?08:34
brokensyntax joined08:35
sveinse I can do anything on my own computer to fetch and manipulate whatever I'd like08:35
I just need to come up with some way of evaluating what changes there are between our mirror and the upstream repo08:36
kadoban sveinse: Then just clone one of them, and add the other as a remote. Then fetch. Then you can compare branches fine08:36
Muzer left08:37
cdown_ joined08:37
kadoban !lol should work fine, or gitk --all, both good first glances.08:37
gitinfo A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all08:37
sveinse kadoban: right. Thanks08:38
buddyq left08:38
JeroenT left08:39
JeroenT joined08:39
kadoban Any logs or diffs really are possible, you just need to use the right refs origin/whatever otherremote/whatever, etc.08:39
Wulf joined08:39
liuzhen left08:39
cdown left08:40
a_thakur joined08:41
chll_ joined08:42
cdown_ left08:44
b100s joined08:45
govg left08:46
liuzhen joined08:47
phanimahesh joined08:47
serycjon joined08:47
Muzer joined08:49
acetakwas joined08:49
b100s left08:50
troulouliou_div2 joined08:50
osse fetching is quite harmless, and you have to do that at some point anyway08:50
xall joined08:51
skunkz joined08:51
osse ohh08:53
you need auth to just download stuff without using them ? :O08:54
thebope joined08:55
qpdb left08:56
albel727 joined08:57
JeroenT left08:57
JeroenT joined08:57
Learath2 left08:58
mischat joined08:59
thebope left08:59
JeroenT_ joined09:01
liuzhen left09:03
omegak left09:04
brk_ left09:04
JeroenT left09:05
sagerdearia joined09:05
netj left09:06
liuzhen joined09:06
netj joined09:06
nettoweb joined09:07
rkazak left09:07
_ikke_ Note that fetches do not update the local branches (hg fetch == git pull)09:08
jbitdrop joined09:08
_ikke_ So the changes you fetch are isolated from the local branches09:08
jgrasser joined09:08
kajnc joined09:09
JeroenT_ left09:09
omegak joined09:09
ochorocho__ joined09:10
brk_ joined09:11
liuzhen left09:11
ochorocho__ left09:14
JeroenT joined09:15
lindenle joined09:15
liuzhen joined09:16
kajnc left09:16
kajnc joined09:16
Jameser left09:17
achadwick joined09:18
albel727 left09:19
alcohol joined09:19
kajnc left09:19
lindenle left09:19
govg joined09:20
qpdb joined09:23
timothy left09:27
drizztbsd joined09:27
drizztbsdtimothy09:27
skyfaller joined09:28
courrier joined09:30
afuentes joined09:32
ahr3n joined09:32
dan2k3k4 left09:32
skyfaller left09:32
timothy left09:33
drizztbsd joined09:33
nowhereman joined09:33
drizztbsdtimothy09:33
timothy left09:35
buddyq joined09:35
drizztbsd joined09:35
drizztbsdtimothy09:35
qpdb left09:35
nd left09:40
GT4066 left09:40
aidalgol left09:40
jstimm_ joined09:40
buddyq left09:40
jstimm left09:41
shaggycat left09:43
TheHackOps joined09:44
liuzhen left09:44
TheHackOps gpg: skipped "XXXXXXXXXXXX": secret key not available09:44
Anyone ever fixed this pain in the butt09:44
shaggycat joined09:45
systemovich left09:46
nd joined09:47
timothy left09:48
drizztbsd joined09:48
systemovich joined09:48
drizztbsdtimothy09:48
troulouliou_div2 left09:48
timothy left09:50
drizztbsd joined09:50
nikivi joined09:51
PCatinean joined09:51
drizztbsdtimothy09:51
tobiasvl TheHackOps: is your secret key available?09:51
what are you trying to do, signing a commit?09:52
timothy left09:52
drizztbsd joined09:52
drizztbsdtimothy09:52
TheHackOps tobiasvl, yep09:52
ok09:52
whoops09:52
wrong window09:53
tobiasvl, Yes I have generated it with gpg2 --key-gen and verified it exists09:53
gitinfo set mode: +v09:54
TheHackOps kewl09:54
Anyway back to the point, been googleing lots and everyone just says the same things, I have tried setting it all up using git configure09:54
Seems to give the same error, am i missing something?09:54
tobiasvl TheHackOps: what have you configured?09:55
should be enough to set user.signingkey09:55
ahr3n left09:55
tobiasvl also make sure $GNUPGHOME is set09:55
liuzhen joined09:55
TheHackOps AH09:55
Maybe i missed that last one09:55
thebope joined09:56
star_prone left09:56
star_prone joined09:57
harish_ left09:57
Endarked left09:59
thebope left10:00
makinen joined10:00
brk_ left10:01
makinen git commit is going to add some files I don't want to be added. How do I prevent it?10:01
I probably added them by accident in first the place10:02
corsibu left10:02
qpdb joined10:02
corsibu joined10:03
eduardas_m left10:03
JuliusN makinen: do you want to unstage staged files before committing?10:03
ShapeShifter499 left10:03
JuliusN git reset filename10:04
grawity and later, add them to .gitignore and commit that10:04
JuliusN git reset without filename unstages all changes10:04
Alienpruts left10:05
makinen yea probably they're some temporary files by emacs10:05
selckin 'git status' outputs tells you how10:05
makinen I want to leave the files in the file system as they were10:07
corsibu left10:07
makinen but I don't want them to be committed or pushed to the origin10:07
I'm not sure if git reset is what I want to do10:08
selckin it is10:08
nikivi left10:09
JeroenT left10:09
makinen ah yes it was, thx :)10:09
JuliusN i have an another issue. yesterday i merged my branch with origin/master and resolved all conflicts, but today when i try to merge again i get (seemingly) the same conflicts. i was wondering if i may have made some common newbie mistake?10:10
mischat left10:10
JuliusN yesterday i created a new branch before committing the merge10:11
this is the branch in which i'm currently trying to pull from master10:11
Macaveli joined10:12
rnsanchez joined10:13
brk_ joined10:13
BadSnappa joined10:14
Jameser joined10:15
govg left10:15
mehola left10:19
jeanres joined10:19
jeanres left10:19
jeanre joined10:20
jeanre hi all, we merged a branch and reverted it, now we cannot merge it again, it says there are no changes10:20
but when I go into the branch I want to merge into master10:20
the changes are there10:20
I just can't do git merge [Branch]10:20
netj left10:21
netj joined10:21
jnewt joined10:21
tlaxkit left10:22
tlaxkit joined10:22
cagedwisdom left10:27
_ikke_ jeanre: a revert does not undo the merge, only the changes in that merge10:28
jeanre: from git points of view, everyting from that branch has already been merged (only later reverted again)10:29
alhariel joined10:29
_ikke_ jeanre: Easiest is to revert the revert again10:29
jeanre yeah10:29
ShekharReddy joined10:29
jeanre did that10:29
but its messy10:29
Jameser left10:32
gniourf left10:32
dan2k3k4 joined10:32
corsibu joined10:33
freimatz joined10:36
Derperperd left10:36
anotheryou_ joined10:39
ferr joined10:40
JeroenT joined10:41
nilg joined10:41
Guest26 joined10:42
Ryanar joined10:44
tobiasvl jeanre: !faulty_merge10:45
gitinfo jeanre: If you have published a merge commit that turned out to be faulty and you'd like to get rid of it, you're probably not going to have a good time. Here's the full story: https://raw.github.com/git/git/master/Documentation/howto/revert-a-faulty-merge.txt10:45
tobiasvl maybe we should have a rerere trigger10:45
maret left10:45
gitinfo set mode: +v10:45
jimi_ joined10:45
tobiasvl JuliusN: but you might want man git rerere10:46
gitinfo JuliusN: the git-rerere manpage is available at http://jk.gs/git-rerere.html10:46
gniourf joined10:46
zulutango left10:47
JuliusN my coworker suggested rebase10:47
jeanre left10:47
NitroLux joined10:47
dmc second time hearing about rerere in two days.. better see wth it is10:47
oic10:47
rominronin left10:48
rominronin joined10:48
Alienpruts joined10:48
tobiasvl JuliusN: sure, you can rebase, that's an alternative to merging10:49
rominronin left10:49
rominron_ joined10:49
evanwang left10:49
jeanres joined10:49
tobiasvl re-reading your initial question I agree with your coworker, looks like you want to rebase10:49
ieee joined10:50
JuliusN thanks10:51
also he suggested that we should keep something he called 'research master', a branch that we should merge with origin/master regularly, and derive all our feature branches from the research branch10:53
makinen left10:53
tobiasvl sure, that's not an uncommon workflow – although usually this is called a "dev" branch, in case you run into it in online literature10:54
!workflow10:54
gitinfo Finding the right workflow for you is critical for the success of any SCM project. Git is very flexible with respect to workflow. See http://sethrobertson.github.com/GitBestPractices/#workflow for a list of references about choosing branching and distributed workflows.10:54
thebope joined10:57
soerenb_ joined10:59
sorenb left10:59
grift left10:59
grift joined10:59
thebope left11:01
CussBot left11:04
xkr47 joined11:05
CussBot joined11:05
liuzhen left11:05
Jameser joined11:06
roelmonn_ joined11:08
irco joined11:08
soerenb_ left11:08
soerenb_ joined11:09
roelmonn_ left11:09
roelmonn_ joined11:09
mischat joined11:11
rafalcpp joined11:11
ochorocho__ joined11:11
roelmonnens left11:12
ahmedelgabri left11:12
JeroenT left11:13
mischat_ joined11:13
Jameser left11:14
Jameser joined11:15
ochorocho__ left11:15
mischat left11:16
stfn left11:16
Vinnie_win_o joined11:17
Vinnie_win left11:18
soerenb_ left11:18
soerenb_ joined11:19
ocbtec joined11:19
JeroenT joined11:21
Shentino left11:22
ojdo left11:23
rominron_ left11:24
rominronin joined11:25
SpeakerToMeat joined11:25
grayjoc left11:25
fuchstronaut joined11:25
mizu_no_oto joined11:27
Macaveli left11:29
skyfaller joined11:29
Alienpruts left11:29
skunkz left11:29
stfn joined11:29
skunkz joined11:30
rominronin left11:30
fuchstronaut left11:30
ojdo joined11:30
Guest35924 left11:30
fuchstronaut joined11:30
Alienpruts joined11:31
umpc joined11:31
Macaveli joined11:32
qpdbGuest6529211:32
Guest65292 left11:32
qpdb joined11:32
skyfaller left11:34
nuck joined11:36
nuckGuest6739111:37
buddyq joined11:38
mischat_ left11:38
rominronin joined11:38
buddyq left11:42
liuzhen joined11:43
Jameser left11:43
Haliucinas left11:44
liuzhen left11:45
johnmilton left11:45
corsibu left11:46
brokensyntax left11:47
corsibu joined11:47
Gonzo89 joined11:48
jimi_ left11:48
brokensyntax joined11:48
brk_ left11:48
rendar left11:50
corsibu left11:51
aupo joined11:52
brk_ joined11:52
aupo Hey, I have a question on the inner workings of git URLs if anyone could enlighten me.11:53
What does git do with this URL exactly: "git+ssh://git@git.rd.company.com:repo/package.git#branch"11:53
Most specifically the ":repo/package..." part, how is that interpreted and or how should it be interpreted?11:53
canton7 "git+ssh://" isn't a valid git url, afaik11:54
':repo/package.git' is a file path, relative to 'git's home directory, to the repository to interact with11:54
aupo Oh yeah, shit, I copied that from a very old file11:54
canton7 but the '#branch' stuff is non-standard as well11:54
aupo "ssh://git@git.rd.company.com:repo/package.git" this is what I should be asking, of course11:55
canton7 that's also invalid11:55
ssh:// urls interpret the stuff after ':' as a port11:56
see 'git urls' in man git clone11:56
gitinfo the git-clone manpage is available at http://jk.gs/git-clone.html11:56
corsibu joined11:56
aupo This one works, though... Althought with npm, so I guess I'm actually barking at the wrong tree here.11:56
canton7 'git@git.rd.company.com:repo/package.git' would be valid, as would 'ssh://git@git.rd.company.com/~/repo/package.git' and 'ssh://git@git.rd.company.com:22/~/repo/package.git'11:56
nowhereman left11:57
aupo Sorry to bother you folks, I guess I'll go bark at #node.js next :)11:57
rchavik left11:57
canton7 it would be really weird if npm had different url syntax to git :11:57
aupo It most definitely seems to have.11:57
thebope joined11:57
canton7 https://docs.npmjs.com/files/package.json#git-urls-as-dependencies yeah, utterly different11:58
aupo Myup..11:58
Guess I'll go read the source code to see, what they actually do with that.11:59
dsdeiz left12:01
aupo left12:02
thebope left12:02
Andrew_K left12:03
pks left12:04
synthroid joined12:04
rendar joined12:04
johnmilton joined12:06
BPL joined12:07
BPL Is it possible to know what are the branches of a certain commit hash?12:07
Endarked joined12:07
xameada left12:08
_ikke_ git branch --contains <hash>12:08
Seban joined12:08
anonymuse joined12:09
TheHackOps left12:10
Eryn_1983_FL left12:11
Seban left12:13
Shentino joined12:13
Endarked left12:14
clmsy joined12:14
ExoUNX joined12:14
fxer joined12:15
Seban joined12:16
t4nk712 joined12:16
Eryn_1983_FL joined12:17
mizu_no_oto left12:18
skyfaller joined12:20
anonymuse left12:20
gtristan left12:23
Macaveli left12:24
re1_ joined12:25
WayToDoor joined12:26
Macaveli joined12:26
Macaveli left12:26
re1 left12:28
brokensyntax left12:28
brokensyntax joined12:29
aavrug left12:30
grayjoc joined12:31
AndrewAlexMac left12:31
modlin joined12:31
mizu_no_oto joined12:34
frobnic left12:34
t4nk712 left12:35
oxsyn left12:36
dsdeiz joined12:36
frobnic joined12:37
davimore_ joined12:38
Gamecubic joined12:38
tjone270 joined12:38
f3r70rr35f joined12:39
buddyq joined12:39
mischat joined12:39
cjbrambo joined12:40
mizu_no_oto left12:40
traxo-xx- left12:40
chele I am reading the manual of gitolite and I see that you can specify a permissions rule for a specific ref relatively to refs/heads giving just the name of it ,e.g master, hotfix-bug111 which would mean refs/master or any branch. you can also specify a rule with an absolute path relative to refs/ e.g. by saying refs/admin/secret-path. what does this mean that the admin/secret-path branch is created under refs/ folder and not under refs/he12:41
ads ?12:41
rnsanchez left12:41
AndrewAlexMac joined12:41
ahmedelgabri joined12:41
davimore__ left12:41
Shakeel_ left12:41
ShekharReddy left12:42
osse chele: it means that git does not consider it a branch. you won't see it's log when you do git log --branches. it doesn't appear in 'git branch' etc.12:43
ij joined12:43
PioneerAxon left12:43
buddyq left12:44
justrohu left12:44
mischat left12:44
PioneerAxon joined12:44
traxo-xx joined12:44
chele so there's is something else to handle such creation of 'it'. And what's this 'it'?12:45
ij Can I do the show/log --format=medium + something else, without repeating the whole thing by hand?12:45
chele osse maybe you can point out to an example ...12:45
osse chele: refs that are in refs/heads are called branches. refs that are in refs/tags are called tags. other refs are just called refs.12:47
JamesBaxter joined12:47
osse not sure what the question is12:47
chele how do you create a ref?12:48
osse chele: if you're badass: echo somesha1value > .git/refs/admin/secret-path12:49
chele: normal people use git update-ref12:49
halbomin left12:50
WayToDoor left12:50
shinnya joined12:52
sagerdearia left12:52
xameada joined12:54
fxer left12:54
gho5t joined12:55
osse chele: e.g. git filter-branch uses git update-ref when it creates the backups in refs/original12:55
concerti joined12:57
eindoofus joined12:58
jimi_ joined12:59
thebope joined12:59
ij Is git log just a commit range generator that "maps" the range over to git show?13:00
joki joined13:00
roelmonn_ left13:00
roelmonnens joined13:01
nowhereman joined13:01
tlaxkit left13:01
thiago left13:01
tlaxkit joined13:01
Lor_ left13:02
_ikke_ I don't think that's an accurate description13:03
git show can show all sorts of objects13:03
thebope left13:04
chele osse so you could have a ref to a refs/private-area/awesome-hacks/ (for instance) where you do dirty stuff and when finished your offer to some integration guy to take it from there and merge to master branch and thus avoiding the creation of a specific repo, right?13:05
anonymuse joined13:05
osse chele: yes13:05
chele: that said, I'd rather create my own repo to avoid that :p13:05
chele is not best practice or?13:06
osse just seems messy to me13:06
Repox left13:06
modlin left13:07
chele osse well haven't found a way to do it w/o installing say standalone gitlab.13:07
cause forking is not in git13:07
harish_ joined13:07
cdg joined13:08
sorenb_ joined13:09
soerenb_ left13:09
anonymuse left13:09
LBV_User joined13:10
chele osse that or you could still create branches prefixing your username (uniq. dev id) and so this integration guy can merge from it..13:11
osse chele: if you don't have a fancy github/gitlab-like thingy then maybe this is easier.13:11
chele osse no I don't13:12
osse I think gitolite can do it as well (ie. easy creation of forks) but I don't know holw13:12
chele hm13:12
Noldorin left13:12
chele yes i was exploring the configuration of gitolite and noticed the permission rules allow that.13:13
canton7 gitolite can do that, yep13:13
Eryn_1983_FL hi guys so i wrote a script to do my pushing and pull for releases in puppet repo13:13
ayogi left13:13
Eryn_1983_FL can you check it out real quick? if i am doing it right13:14
fyi this is in my repo /home/THRACE/erin/puppet/manifests/release.txt13:14
http://sprunge.us/JMFC13:14
star_prone left13:15
joki left13:15
acetakwas left13:15
govg joined13:16
Gsham joined13:16
acetakwas joined13:17
Noldorin joined13:17
lindenle joined13:18
Haliucinas joined13:18
Haliucinas left13:18
anotheryou__ joined13:19
CEnnis91 joined13:19
troulouliou_div2 joined13:20
joki joined13:20
Seban left13:21
lindenle left13:22
mischat joined13:23
anotheryou_ left13:23
subhojit777 left13:23
sagerdearia joined13:25
armin left13:25
armin joined13:26
selckin thats gonna fuck so much up if any of them fail13:27
ayogi joined13:27
Seban joined13:29
Raging_Hog left13:30
serycjon left13:31
overlord_tm left13:31
frobnic left13:32
courrier left13:32
chele osse would you state some reasons behind forking own repo vs having personal branching architecture?13:34
star_prone joined13:34
frobnic joined13:34
troulouliou_div2 left13:35
nettoweb left13:35
buddyq joined13:36
osse chele: my main reasons are that you can force-push as much as you like and that you don't pullute other people's repos13:37
when they run 'git branch -a' or -r they'll see your crap13:37
nettoweb joined13:37
corsibu left13:37
Dougie187 joined13:38
corsibu joined13:38
arooni joined13:40
jstimm_ left13:41
griffindy joined13:41
ayogi left13:41
BPL _ikke_: Tyvm, it works, i guess git branch --contains hash will return the local ones only, isn't?13:42
Gsham left13:42
Darcidride joined13:42
qpdb left13:43
corsibu left13:43
navidr joined13:44
grayjoc left13:44
_ikke_ yes, use -a to also include remote tracking branches13:44
malcon joined13:44
frobnic left13:45
frobnic_ joined13:45
joki left13:45
re1_ left13:45
saml left13:46
anotheryou joined13:46
cso joined13:47
DeltaHeavy joined13:47
star_prone left13:47
frobnic_ left13:48
frobnic joined13:48
saml joined13:48
anotheryou__ left13:49
yqt joined13:49
grayjoc joined13:50
joki joined13:50
troulouliou_div2 joined13:50
kajnc joined13:50
cso left13:51
mischat_ joined13:52
sdothum joined13:52
nettoweb left13:53
ash_workz joined13:53
kajnc left13:54
mischat left13:54
mischat_ left13:54
kajnc joined13:54
mischat joined13:55
nettoweb joined13:55
nettoweb left13:55
boombatower joined13:55
liuzhen joined13:55
jknetl left13:56
mischat_ joined13:57
mischat_ left13:57
frobnic_ joined13:57
frobnic left13:57
mischat_ joined13:57
jeffreylevesque joined13:57
anonymuse joined13:58
Gsham joined13:58
\du left13:59
mischat left13:59
VladGh left13:59
zivester joined14:00
raphink joined14:00
VladGh joined14:01
barteks2x left14:02
star_prone joined14:02
Xethron joined14:02
fahadash joined14:03
sorenb_ left14:03
NitroLux left14:03
sorenb_ joined14:04
tlaxkit left14:04
Ryanar left14:04
Gsham_ joined14:04
b_jonas joined14:04
Gsham left14:04
sangy joined14:05
b_jonas Hi. git help rev-parse documents all the magical syntax I can use in git when it expects an object, right?14:05
But I hear there's also some magical syntax for when git wants filenames. Where is that documented?14:06
Eryn_1983_FL selckin: yeah.. trying to figure out what to do about that14:07
davimore__ joined14:08
ResidentBiscuit joined14:08
AaronMT joined14:08
davimore joined14:10
davimore_ left14:11
Eryn_1983_FL selckin: so what do you suggest i do if i cant do a script?14:11
kajnc left14:11
PioneerAxon left14:11
PioneerAxon joined14:11
selckin at least push only at the end14:11
brillenfux left14:12
davimore__ left14:13
modlin joined14:13
Eryn_1983_FL ok14:14
matsaman joined14:14
LocusAsaf joined14:15
joki left14:15
buddyq so, I just did a git push origin origin/my_branch and it said: * [new branch] origin/Buddys_branch -> origin/Buddys_branch. But the branch already existed14:16
LocusAsaf Let's say I have Two branches that I consider trunks, qa & dev which most people will branch from for normal development. Is it possible to detect with 100% certainty which trunk the branch is from?14:16
buddyq Then it says: Your branch is ahead of 'origin/Buddys_branch' by 2 commits.14:17
JeroenT left14:17
patarr joined14:18
thiago joined14:18
mangolisk joined14:18
thebloggu joined14:18
qt-x left14:18
nikivi joined14:19
joki joined14:20
osse buddyq: u don fukt up.14:22
just kidding14:22
buddyq: you probably have made branch called 'origin/Buddys_branch'. that's quite different from a branch called 'Buddys_branch' located at 'origin'14:23
buddyq nah, I resolved it actually. Looks I got the ssh key thing worked out.14:23
ah!14:23
really??14:23
maybe thats what happened...14:23
fb| joined14:23
phanimahesh yep. * [new branch] origin/Buddys_branch -> origin/Buddys_branch was a hint14:23
osse buddyq: do git for-each-ref | grep Buddys14:23
synthroid left14:23
buddyq How should I push my local brnach to github?14:23
^7heo Is my submodule directory (.git/module/<module>/) supposed to contain the files that are checked in my submodule?14:23
_ikke_ buddyq: git push origin <branch>14:24
LocusAsaf anyone know the answer to my question, or is it not possible?14:24
buddyq i get 3 results14:24
^7heo or is it only supposed to contain what would normally be the .git folder of that submodule?14:24
_ikke_ ^7heo: It's supposed to contain the contents of the .git folder for thos submodules14:24
right14:24
buddyq i did git push origin origin/Buddys_branch. Is that wrong?14:24
phaleth joined14:24
^7heo How the fuck did my index content end up there then?!14:24
=/14:24
for some reason14:24
the index points there...14:24
osse buddyq: yes. git push origin Buddys_branch14:25
buddyq They all look correct. I have refs/remotes/origin/Buddys_branch, refs/remotes/host/Buddys_branch, refs/remotes/Buddys_branch14:25
ok14:25
phanimahesh LocusAsaf: git only works with commit graphs. You can look at the history and make an educated guess, but that's all.14:25
commits aren't coupled to branches, so you can never be certain on what branch a commit was made.14:26
kajnc joined14:26
buddyq ah okay. cool.... working now14:26
ferr left14:26
LocusAsaf phanimahesh: Well I'm not focusing on the commits, I just want to branch to branch14:26
ferr joined14:26
LocusAsaf want to know*14:26
phanimahesh LocusAsaf: A branch is just a text file in .git/refs with the id of commit.14:27
So if commits don't track something, branches don't, either.14:27
thiago left14:27
rominronin left14:27
rominronin joined14:28
thiago joined14:28
LocusAsaf speaking in terms of the graph, is it possible to follow the path along until I find a branch that == $SOME_TRUNK ?14:28
rominronin left14:28
rominron_ joined14:28
LocusAsaf programmatically of course14:29
phanimahesh the graph is of commits, each pointing to their previous commit (or commits, in case of merges)14:29
^7heo _ikke_: ok, for the reference, my worktree in the .git/module/<module>/config was pointing at .git/module/<module>/ rather than at ./<module>14:29
_ikke_: that's how things fucked up.14:29
phanimahesh you can follow it, but why would you want to do it?14:30
osse LocusAsaf: to do what?14:30
anonymuse left14:30
anonymuse joined14:30
LocusAsaf phanimahesh: so if I keep following the previous commit and check the branch for each one I would eventually hit another branch, a trunk in my example git process?14:31
Seban left14:31
gesker left14:31
nettoweb joined14:31
Endarked joined14:31
_ikke_ in git, we don't really use the word trunk14:31
LocusAsaf osse: I want to determine which trunk a feature was branched from14:31
patarr left14:31
_ikke_ It's all branches14:31
^7heo _ikke_: depends, if it's in German.14:32
LocusAsaf _ikke_: can't I use the word if that's how I defined my git process for development14:32
plasticboy joined14:32
phanimahesh LocusAsaf: you first have to start at your "trunk" branch, follow back and mark commits as belonging to "trunk". Then trace feature branches backwards till you cross a commit in "trunk".14:32
_ikke_ LocusAsaf: Not if it's confusing to other what you mean14:32
perlpilot LocusAsaf: sounds like you want `git merge-base`14:32
^7heo _ikke_: i.e. trunken14:32
Bysmyyr joined14:32
osse LocusAsaf: find the earliest commit on that branch not on any of the trunks: (git rev-list --reverse branch --not trunk1 trunk2 ), then find which trunk its parent belongs to (git branch --contains foo~1)14:33
eivarv joined14:34
zacts left14:34
phanimahesh Or, you can do as osse suggests.14:34
osse foo = first line of output of the rev-list commadn14:34
LocusAsaf _ikke_: I'll run my scenario again in case you missed it, sorry for any confusion. We use branches qa & dev and treat them as trunks. Both branches current commit corresponds to a deployed version of the code. All features are branched off one of the "trunks". WHat I was asking is a programatic method to determine which trunk a feature was branched from14:34
Bysmyyr hi, I have strange question. If I have file from somewhere git history(only that file). Then I have full git repo. Can I find which commit made that file look like that what I have now. in other words, can I find a last commit of loose file14:35
LocusAsaf osse: I'll give that a try14:35
osse Bysmyyr: that's so easy it's not even funny.14:35
zacts joined14:35
timothy left14:35
mischat_ left14:36
osse Bysmyyr: git hash-object -- file14:36
Bloomberg joined14:36
osse Bysmyyr: now you know the SHA1 of its blob. now recurse through history to find a commit that has that blob14:36
Bloomberg left14:36
JeroenT joined14:36
Bloomberg joined14:37
Bloomberg Hello Room!!14:37
gitinfo Bloomberg: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.14:37
mischat joined14:37
liuzhen left14:37
Bloomberg http://imgur.com/a/PYMhB14:38
a_thakur left14:38
Bloomberg someopne know what means that symbol in my git?14:38
jwest left14:38
Bloomberg doesn't working the autodeploy setting14:38
osse Bysmyyr: hmm, something like. blob=$(git hash-object file); git rev-list --all | while read hash; do if git ls-tree -r $hash | grep -q "blob $blob"; then echo "OMG $hash contains file!! \o/"; fi; done14:38
Endarked left14:39
_ikke_ Bloomberg: It's part of you shell prompt, no clue what it means (your font does not support the characters)14:39
Darcidride_ joined14:39
osse Bysmyyr: this assumes there is a commit in which the file is IDENTICAL. otherwise you'd have to diff and do some heuristics14:39
Bysmyyr osse: ok, thats good, thanks14:39
Bloomberg I have several sites in my server, there are setting with autodeploy, but just this site doesn't works the autodeploy and show this symbol14:40
synthroid joined14:41
brokensyntax left14:41
converge joined14:41
fuchstronaut left14:41
brokensyntax joined14:41
vuoto joined14:42
Darcidride left14:42
thebope joined14:43
Endarked joined14:43
phanimahesh left14:43
shgysk8zer0 joined14:44
dreiss joined14:44
zump left14:44
mrwat joined14:45
joki left14:45
mischat_ joined14:45
davimore_ joined14:46
ahmedelgabri left14:46
mischat left14:48
davimore left14:49
dodobrain left14:49
CheckDavid joined14:50
rominron_ left14:50
grayjoc left14:50
IrishPrime joined14:50
IrishPrime left14:50
rominronin joined14:50
IrishPrime joined14:51
iuk joined14:52
joki joined14:52
raspado joined14:52
isysd joined14:52
e14 joined14:53
overlord_tm joined14:53
ELFrederich left14:53
LocusAsaf osse: for the contains command, is my answer always going to be the last line of output?14:53
iuk Hi! Assuming that the commit history is linear, how to find the nth successor of a commit? Is there a notation analogous to ^ but working in the opposite direction?14:54
ahmedelgabri joined14:54
canton7 iuk, no14:54
git doesn't track the child of a commit14:55
osse LocusAsaf: I don't know.14:55
ShekharReddy joined14:55
rominronin left14:55
_ikke_ A commit can have an infinite number of children14:55
iuk _ikke_: I’m OK iterating over all of them.14:56
_ikke_ which will be created after that commit14:56
LocusAsaf osse: following your instructions the contains command seems to print out several branches, not just one which is why I asked14:56
matsaman ain't that the truth14:56
osse LocusAsaf: a commit can "belong" to several branches14:56
_ikke_ iuk: It's basically iterating over all commits and check the parents14:56
iuk _ikke_: I just thought there was a shortcut for that.14:57
re1 joined14:57
_ikke_ nop14:57
iuk: One assumption can be all commits that have a date later then the commit, but that assumption is easily broken14:57
tlaxkit joined14:58
iamthad joined14:58
ochorocho__ joined14:58
iuk _ikke_: I’m not looking for a general solution. I have a repo with linear history.14:58
jeanres left14:58
perlpilot iuk: if the history is linear, why do you want iterate in reverse?14:59
jstimm_ joined14:59
JeroenT left14:59
iuk perlpilot: It’s a pretty lengthy history. I know the hash of the commit I’m interested in, and I want to know what was right after it.14:59
star_prone left15:00
chele left15:00
iuk Perhaps it’s possible to make `git log` scroll down to a particular commit?15:00
rscata left15:01
Guest6802 joined15:01
iuk I guess I should just dump the whole log into a text file and search.15:01
cdg left15:01
perlpilot /SHA1-of-commit-I-want :-)15:01
iuk perlpilot: Yeah)15:01
perlpilot: Right! Right!15:02
perlpilot: Now I get it. Thanks!15:02
perlpilot sure15:02
JeroenT joined15:02
Gsham_ left15:02
ochorocho__ left15:02
jimi_ left15:03
leeN joined15:03
jstimm_ left15:03
re1 left15:03
LocusAsaf osse: okay, I think perhaps I unintentionally left out some important information from my scenario. So as I said the two features are qa & dev. The piece I forgot was that dev is branched from qa so dev knows about commits in qa as well. Therefore when I followed your instructions and followed a feature of qa up and asked it what branches know about the qa, basically it hit qa, dev & features of both. Anecdotally it seems like the right ans15:03
wer is the last branch output but i"m not sure15:03
re1 joined15:03
gtristan joined15:04
overlord_tm left15:04
roelmonnens left15:04
Renard_Chase joined15:04
Bloomberg left15:05
systemovich left15:05
JeroenT left15:06
dviola joined15:06
Renard_Chase Is there a command that reverts all changes I that I commited today?15:06
LocusAsaf according to git-branch documentation the default sort order is "Sort order defaults to sorting based on the full refname (including refs/... prefix)" but I'm not certain what that means15:06
matsaman Renard_Chase: git reset --hard shasumtocommityouwant15:06
subhojit777 joined15:06
jwest joined15:06
Shentino left15:07
aarobc joined15:07
jimi_ joined15:07
govg left15:07
Renard_Chase matsaman : Thank you15:08
Renard_Chase left15:09
Guest26 left15:09
ThomasLocke left15:09
iuk left15:09
SrPx_ joined15:09
jeanres joined15:10
SrPx_ left15:10
stomplee joined15:10
patarr joined15:14
thiago left15:14
barteks2x joined15:14
ShekharReddy left15:15
danslo joined15:15
Guest6802 left15:16
raphink left15:16
brk_ left15:16
JamesBaxter left15:16
nilg left15:17
joki left15:19
al-damiri joined15:20
zeroed left15:20
Gsham joined15:20
Jameser joined15:23
rbern left15:23
e14 left15:24
timothy joined15:24
Vinnie_win_oVinnie_win15:25
nikivi left15:25
aarobc left15:26
patarr left15:26
Balliad left15:27
crose joined15:28
shirty left15:29
ahmedelgabri left15:29
kajnc left15:29
ahmedelgabri joined15:30
diogenese left15:31
e14 joined15:31
matsaman left15:31
matsaman joined15:31
diogenese joined15:32
eivarv left15:32
JamesBaxter joined15:32
fuchstronaut joined15:32
fuchstronaut left15:32
fuchstronaut joined15:32
anonymuse left15:33
bernardio joined15:33
rbern joined15:33
Xethron left15:33
PCatinean left15:34
shgysk8zer0 left15:34
maret joined15:35
flaviodesousa left15:35
lindenle joined15:36
clmsy left15:36
Derperperd joined15:37
synthroid left15:37
khisanth__Khisanth15:37
LBV_User left15:38
eivarv joined15:38
Ryanar joined15:39
vuoto left15:41
sdlnv_ joined15:41
kajnc joined15:42
danslo left15:42
lordjancso left15:42
star_prone joined15:43
kpease joined15:44
isysd left15:45
sdlnv_ left15:45
rnsanchez joined15:46
Alienpruts left15:47
star_prone left15:47
danlovesppipes joined15:48
danimal2 joined15:50
danimal2 hi guys, question..if i do a git pull from a repo on github, then run composer update, will that update all code so any changes i might have made own my own, would be overwritten? i have not forked the repo or do PR's etc..15:51
oskarkv joined15:51
rominronin joined15:51
patarr joined15:52
afuentes left15:52
danlovesppipes left15:52
danimal2 essentially there is some key code i want added in, that the author wont merge...and i want to keep my repo up to date with my changes and the author changes...except for my tweaks.15:52
qpdb joined15:53
alex1a_ joined15:53
Gsham left15:53
alex1a left15:54
Learath2 joined15:54
brokensyntax left15:55
littleforest joined15:55
synthroid joined15:55
afuentes joined15:55
synthroi_ joined15:56
re1_ joined15:57
shiriru joined15:57
re1 left15:57
Gsham joined15:58
einnjo joined15:58
jnavila left15:58
brokensyntax joined15:59
synthroid left16:00
pumafied joined16:00
osse pull performs a merge16:00
between whatever you pull and HEAD16:01
Remram left16:01
ygeLN joined16:02
danimal2 right, thanks osse. so best practice would be fork the repo..commit my changes, likely 1 time changes..then how does my fork stay up to date with the author's commits on github?16:02
rbern left16:02
osse danimal2: you pull from the original and push to your fork16:02
chamunks joined16:02
osse if it's just one commit you need as a patch to make things work I suggest pull --rebase16:02
that way your patch is always on top16:03
Darcidride_ left16:03
xavca joined16:03
danimal2 oh i get it..makes sense. thanks for that rebase tip.ill try that.16:03
osse++16:03
osse !karma16:03
gitinfo This channel tracks karma based on who has gotten lots of thanks for being helpful. If you want to help someone reach karmic nirvana, please mention their name when thanking them with "thank you", "thankyou", "thanks", "thx" or "cheers". Try ".karma <nick>" or ".topkarma" to show karma status of a person.16:03
osse .karma osse16:03
gitinfo the Genuine Real Life Karma™ REST API results are back! o‍sse: 250 (3 in past 30 days) (6 given out)16:03
osse awwww yisss16:03
Remram joined16:04
Gonzo89 left16:04
osse oh, it doesn't count nick++ ?16:04
danimal2 not sure..im not an irc guru either16:04
i was trying to give you good karma16:04
EvilPenguin joined16:04
Erati joined16:05
nettoweb left16:05
xavca left16:05
osse jast: plz fix16:05
i need my karma16:05
danimal2 thank you osse16:06
lol!16:06
osse that should do it16:06
ochorocho__ joined16:06
subhojit777 left16:06
Zarthus Does anyone know of a good resource for a 5-10 minute introduction to git. Something that doesn't explain it entirely, but does give them an introduction. Something like "homework you should look at before I tell you how to use it". I don't expect to advance beyond pull/push.16:06
albel727 joined16:06
mangolisk left16:07
Zarthus A video might be ideal, but I don't really care in what format it is in.,16:07
osse Zarthus: any prior knowledge with VCSes?16:07
Zarthus None, they're complete novices.16:07
subhojit777 joined16:07
Zarthus I plan to explain it to them in person, but won't see them until next week.16:07
danimal2 Zarthus, im sure there's bazillions on YT..just my .0216:07
mischat joined16:08
madewokherd joined16:08
Zarthus I looked at the GitHub youtube account and it's boring as hell.16:08
osse !videos16:08
gitinfo [!talks] Some good video talks about Git: [yt] http://goo.gl/z72s (Linus Torvalds: History&Concepts); [yt] http://goo.gl/R9H2q (Scott Chacon: Git basics, live examples); http://vimeo.com/35778382 (Randal Schwartz: Git basics, descriptional); http://vimeo.com/46010208 (Jesica Kerr: Git basics, descriptional)16:08
jknetl joined16:08
uofxj joined16:08
Zarthus I bet the Linus Torvalds one is going to be fun16:08
osse the first few minutes of the Jessica Kerr one are good imho16:08
the whole is longer than 10 minutes though16:08
Zarthus I don't really mind.16:09
Jameser left16:09
danimal2 Zatrthus,what helped me alot as a newb was Sourcetree if they are working on windows.16:09
Zarthus I'm recommending they install Github For Desktop/SmartGit/Sourcetree, but that's kinda offtopic here.16:09
tlaxkit left16:10
shakalaka left16:10
mischat_ left16:10
Guest26 joined16:11
osse I don't have much experience with any of those, but I do recommend that you stay as far away from tortoisegit as possible16:11
uofxj left16:11
_cyril_ joined16:11
Zarthus yep, I had horrible experiences with that.16:11
SmartGit was how I got introduced to git, it's pretty neat -- until I broke things and someone else had to fix things.16:12
aswen left16:12
Zarthus I love how Jessica Kerr is shitting on subversion16:12
danimal2 yeah Tortoisegit i remember hosed me more than once...years ago when i fooled with it.16:12
shakalaka joined16:13
grayjoc joined16:13
Zarthus I fear this video might still be a bit too technical.16:13
miklcct joined16:14
osse Zarthus: btw, she's given this talk in a more refiner manner later. but i like the whiteboard etc. it makes stuff more intuitive. I've personally had much success in writing "HEAD" and "master" on a couple of stickies to explain stuff16:14
mischat left16:15
fedepad left16:15
jeanres left16:15
mischat joined16:15
Zarthus They're telling us to start a 6 man project without any explanation of version control. And I'm not looking forward to using dropbox on a 6 man project.16:15
osse Zarthus: the one by scott chacon is really good too.16:15
_ikke_ Zarthus: Same when I went to school. Discovered version control ourselves16:16
dreiss left16:16
jeanres joined16:16
Zarthus _ikke_: in week 6 of the first year? :P16:16
eshlox left16:16
_ikke_ Zarthus: probably16:16
Zarthus Did you use any resources to teach them/yourself?16:16
_ikke_ Started with SVN at the time, but for git, !books has good resources16:17
gitinfo [!book] There are several good books available about git; 'Pro Git' is probably the best: http://git-scm.com/book but also look at !bottomup !cs !gcs !designers !gitt !vcbe and !parable16:17
_ikke_ and questions on stackoverflow16:17
danimal2 Zarthus, i dont work as part of a team,just solo dev with my own repos..what made it clear for me is just make ur changes, test, when all good, Commit, then push to your remote repo if necessary.16:17
_ikke_ !parable is good if you want to explain or learn the principles of version control16:18
gitinfo 'The git parable' provides some good reasoning behind git. http://tom.preston-werner.com/2009/05/19/the-git-parable.html16:18
albel727 left16:19
albel727 joined16:19
davimore__ joined16:19
LocusAsaf left16:19
dan2k3k4 left16:19
EvilPenguin left16:20
shiriru left16:20
danimal2 nice link, thank you _ikke_16:20
cyan__ left16:20
Guest26 left16:21
svm_invictvs left16:21
JamesBaxter left16:21
Guest26 joined16:21
Zarthus I've dumped some resources in our distributed dropbox. Hopefully they take the time to read/watch some of it16:22
thanks!16:22
davimore_ left16:22
Gsham left16:22
Shentino joined16:22
EvilPenguin joined16:22
_ikke_ yw16:23
nitric joined16:24
skunkz left16:24
Serpent7776 left16:25
_geoff joined16:25
Exagone313 Hi, I'd like to fork and maintain a project that uses git, but I'm not very familiar with. I wrote this scheme of local repo I could use http://dpaste.com/0VMN2QJ Is it bad? I don't know yet how would I succeed to do that but I'll search. Thanks for your help.16:25
rominronin left16:25
Derperperd left16:28
alfism joined16:28
eshlox joined16:28
cdg joined16:29
blackwind_123 left16:29
kurkale6ka left16:30
jstimm joined16:31
Gsham joined16:32
JamesBaxter joined16:32
LionsMane joined16:32
mikecmpbll left16:33
Pieplay left16:33
[Brain] joined16:33
patarr left16:33
encod3 left16:34
hahuang65 joined16:34
mischat_ joined16:34
blackwind_123 joined16:34
pks joined16:35
Derperperd joined16:35
fahadash left16:36
Derperperd left16:37
mischat left16:37
robotroll joined16:37
a_thakur joined16:37
brokensyntax left16:38
synthroid joined16:38
manuel joined16:38
svm_invictvs joined16:38
LeBlaaanc joined16:40
mischat joined16:40
hahuang65 left16:40
synthroi_ left16:41
mischat left16:41
LeBlaaanc left16:41
mischat joined16:42
Gsham left16:42
_August_ joined16:42
nilg joined16:42
brokensyntax joined16:42
mischat_ left16:43
hahuang65 joined16:43
_cyril_ left16:45
_August_ I have a branch that im trying to merge the changes to another branch but im wondering how can I merge the change into another branch under a single commit instead of all the commits from the branch im merging from. So how can I take 5 commits and combine them into a single commit?16:46
osse merge --squash16:46
brokensyntax left16:46
brokensyntax joined16:47
_August_ so git merge --squash "merge title" ?16:47
anonymuse joined16:47
_August_ osse ^^16:47
kulelu88 joined16:48
osse where did you get that from?16:48
write the merge liek you would otherwise, but add --squash to it16:48
_August_ ohh ok16:48
durham joined16:48
overlord_tm joined16:49
anonymuse left16:51
mischat_ joined16:51
_cyril_ joined16:52
LeBlaaanc joined16:52
skunkz joined16:52
Skryll joined16:53
achadwick left16:53
shakalaka left16:54
gniourf left16:54
flavius joined16:54
shakalaka joined16:54
DeltaHeavy left16:54
mischat left16:55
SteffanW joined16:56
buddyq left16:58
cyan__ joined16:58
yohnnyjoe joined16:59
foist joined16:59
_August_ osse: Why when i try to push the merge it keeps saying everything up to date and doesnt push?16:59
notebox joined16:59
_August_ i pull everything to make sure it was current16:59
SamuelAlderson joined17:00
_August_ wait... when i squash everything do i have to recommit them?17:01
X-Kent joined17:01
roelmonnens joined17:01
synthroid left17:01
jstimm left17:02
X-Kent hi, I have checked out, master, then did "git checkout remotes/origin/name_of_branch". Now I am in "detached" state and it didn't seem to update anything, how do I switch a remote branch ?17:02
osse _August_: yes, you have to run git commit after17:02
X-Kent: !detached17:02
gitinfo X-Kent: A detached HEAD(aka "no branch") occurs when your HEAD does not point at a branch. New commits will NOT be added to any branch, and can easily be !lost. This can happen if you a) check out a tag, remote tracking branch, or SHA; or b) if you are in a submodule; or you are in the middle of a c) am or d) rebase that is stuck/conflicted. See !reattach17:02
_August_ Got it, thanks17:02
X-Kent !reattach17:03
gitinfo Letters refer to !detached. (a) and (b): 'git checkout branchname' to continue working on another branch, or 'git checkout -b branchname' to start a new one here; (c) git am --continue; (d) git rebase --continue17:03
SamuelAlderson left17:03
osse X-Kent: if you only wanted to checkout the remote branch to look at it, test it, compile it, whatever, then being detached is completely fine17:03
jeffreylevesque left17:03
Guest26 left17:03
osse if you want to work on it, do the checkout -b thing17:03
X-Kent osse, nope, I did my code on the master and now I need to deliver it to another branch, I can't figure out how to get anything pointing to that remote branch so I can merge and commit17:04
osse, I tried checking out master again and then branching but it became detached17:05
Gsham joined17:05
elect left17:05
osse X-Kent: to update a remote branch you push17:05
X-Kent osse, yea I mean commit and then push, but I can't get a working copy that has that branch as a remote17:06
albel727 left17:06
albel727 joined17:06
osse then you did something wrong17:06
!repro17:06
gitinfo [!transcript] Please paste (using https://gist.github.com/ or similar) a transcript ( https://git.io/viMGr ) of your terminal session so we can see exactly what you see17:06
Gsham left17:06
X-Kent is there a way to just checkout that new branch ?17:07
tyreld joined17:07
osse which new branch?17:07
the remote one? no.17:07
notebox left17:07
albel727 left17:07
dendazen joined17:08
X-Kent osse, when I do "branch -a" in my master I see it as "remote/originin/branch_name"17:08
albel727 joined17:08
albel727 left17:08
albel727 joined17:08
X-Kent and git shows that my current is "remotes/origin/HEAD"17:08
how do I switch it to "remote/origin/branch_name" ?17:09
osse what happened when you tried to do what you were recommended ?17:09
X-Kent I tried "git branch remote/origin/branch_name", now it says it's detached and I can't pull/push17:09
osse you need to create a LOCAL branch named 'branch_name'17:10
thiago joined17:10
osse which git checkout -b branch_name will do if you have checked out remotes/blablba previously17:10
X-Kent I didn't checked out remotes/blala, always worked on master17:11
mikecmpbll joined17:11
robotroll left17:11
osse the first thing you said when you join was that you did17:11
X-Kent so, in my master I do "get checkout -b branch_name" and then pull ?17:11
CalimeroTeknik joined17:12
osse X-Kent: "I have checked out, master, then did "git checkout remotes/origin/name_of_branch". Now I am in "detached" state"17:13
is this still true?17:13
X-Kent osse, I already deleted that and checkout again clean master17:13
osse git checkout -b branch_name origin/branch_name17:13
anonymuse joined17:14
X-Kent just a sec17:14
lus joined17:14
_ADN_ left17:15
durham_ joined17:16
troulouliou_div2 left17:16
brokensyntax left17:16
brokensyntax joined17:17
durham_ left17:17
X-Kent osse, it says "Branch branch_name set up to track remote branch branch_name from origin." and "Switched to a new branch 'branch_name'"17:17
a_thakur left17:17
osse fantastic17:17
X-Kent osse, I can now pull ?17:17
osse now you have a local branch you can work in, and if you run 'git push' stuff gets push to the remote equivalent17:17
durham_ joined17:17
osse X-Kent: yes17:17
X-Kent osse, that's perfect, thank you !17:17
Alienpruts joined17:17
X-Kent osse, git is really hard when you are used to svn17:18
LeBlaaanc left17:18
durham left17:19
osse X-Kent: since you've already done work in master you can copy that over to this branch by using cherry-pick17:19
kajnc left17:19
synthroid joined17:19
X-Kent osse, I will just run "meld" and merge it there manually :-)17:19
dreiss joined17:20
joki joined17:20
pks left17:21
b_jonas If I run (git diff --cached -- foo) then the foo is relative to the working directory, but in (git diff --cached -- :/foo) the foo is relative to the repository root.17:21
Where is that syntax documented in the git manpages?17:21
maret left17:21
b_jonas I know that git help rev-parse documents all the syntax for arguments that denote objects, but this is a filename argument.17:21
I'd like to know what all the syntax for filename arguments is.17:22
pks joined17:22
dsantiago left17:22
cyan__ left17:22
rominronin joined17:22
converge left17:23
osse b_jonas: man gitglossary, under 'pathspec'17:23
gitinfo b_jonas: the gitglossary manpage is available at http://jk.gs/gitglossary.html17:23
osse (don't blame me. I didn't put it there)17:23
buddyq joined17:24
raphink joined17:24
EvilPenguin left17:24
b_jonas osse: thank you, that's where it is!17:24
marcogmonteiro left17:24
b_jonas I'll have to read that carefully17:24
wget left17:24
b_jonas I must admit, I don't really like this magic syntax, because :/ means something completely different as a revision argument17:24
osse b_jonas: very. it's nearly incomprehensible :p17:24
wget joined17:25
wget left17:25
wget joined17:25
b_jonas so without the -- it gets utterly ambiguous17:25
cdown joined17:25
EvilPenguin joined17:26
buddyq left17:26
jimi_ left17:26
shakalaka left17:27
buddyq joined17:27
chrisgeorge joined17:28
albel727 left17:28
shakalaka joined17:28
albel727 joined17:28
chll_ left17:29
e14 left17:29
stuh84 joined17:30
e14 joined17:30
durham_ left17:30
guampa left17:31
durham_ joined17:31
durham_ left17:31
durham_ joined17:32
LocusAsaf joined17:32
Guest6802 joined17:32
LocusAsaf osse: just wanted to let you know that I worked out a reasonable way to solve my problem. I'm walking down the output of revlist until I hit the first commit hash that equals the hash of my trunk heads.17:33
ferr left17:34
kireevco_ left17:34
encod3 joined17:34
X-Kent left17:35
Remram left17:35
LocusAsaf also, I appreciate the help before17:35
davimore joined17:35
JamesBaxter left17:35
kireevco_ joined17:35
xall left17:35
tang^ joined17:36
iosnerd joined17:36
davimore__ left17:36
Guest6802 left17:36
maxxe joined17:36
kireevco_ left17:37
JamesBaxter joined17:37
kireevco joined17:37
cagedwisdom joined17:37
Remram joined17:38
encod3 left17:38
EvilPenguin left17:39
diogenese left17:39
a_thakur joined17:40
jeanres left17:40
kajnc joined17:40
duderonomy joined17:40
subhojit777 left17:40
diogenese joined17:40
duderonomyGuest6082817:40
ronny hi17:41
is there a poreclain command that tells me of a git repo is shallow?17:41
patarr joined17:41
guampa joined17:42
cbreak ronny: does git config count? :)17:43
alex1a_ left17:43
nettoweb joined17:44
raphink left17:44
iosnerd left17:44
PCatinean joined17:44
iosnerd joined17:44
cbreak hmm... I guess you can just look at .git/shallow17:45
raspado left17:45
raspado_ joined17:45
a_thakur left17:45
ronny cbreak: i want to provide an option to user to deide what to do in shallow clones (i.e. fail auto-unshallow or warn that data is incorrect)17:45
WakiMiko joined17:45
roelmonnens left17:45
nettoweb left17:46
anonymuse left17:47
anonymuse joined17:47
umpc left17:48
bernardio left17:48
joki left17:48
nilg left17:49
EvilPenguin joined17:50
shakalaka left17:50
mischat_ left17:51
Sasazuka joined17:51
shakalaka joined17:51
saml left17:52
pothepanda joined17:52
a_thakur joined17:53
freimatz left17:53
davimore_ joined17:54
thiago left17:54
jimi_ joined17:54
PCatinean left17:54
dsantiago joined17:54
PCatinean joined17:56
dsantiag_ joined17:56
dsantiago left17:56
rominronin left17:57
thiago joined17:57
albel727 left17:57
davimore left17:57
khfeng left17:57
albel727 joined17:57
einnjo left17:59
Guest60828 left18:00
fuchstronaut left18:00
duderono_ joined18:00
nettoweb joined18:01
navidr left18:01
ki0 left18:03
mountpoint joined18:03
converge joined18:05
ojdo left18:05
hahuang61 joined18:07
albel727 left18:07
hahuang65 left18:07
albel727 joined18:07
saml joined18:08
khfeng joined18:09
hypercube32 joined18:10
BSAlb left18:11
grayjoc left18:11
BSaboia joined18:11
artisanIndia joined18:12
artisanIndia I have committed some files and then made changes in all of them and then I added some of them into gitignore, now if I do a git reset --soft will that discard the changes as well ?18:13
osse LocusAsaf: Sounds reasonable18:13
jimi_ left18:14
fuchstronaut joined18:14
kajnc left18:14
WayToDoor joined18:14
mibr0 joined18:17
artisanIndia how do I ignore permission changes from the push ?18:18
eyou joined18:18
fedepad joined18:18
fuchstronaut left18:19
a_thakur left18:19
lindenle left18:20
einnjo joined18:21
bocaneri left18:22
vannorden joined18:22
btyne79 joined18:22
CheckDavid left18:23
cagedwisdom left18:24
Darren_ joined18:24
albel727 left18:24
albel727 joined18:24
jstimm joined18:24
canton7 artisanIndia, git doesn't track permissions (except the execute bit)18:26
fahadash joined18:26
vuoto joined18:26
artisanIndia ok18:26
Exagone313 Hi, I'd like to fork and maintain a "mod" of a game, that has a repo on Github. They have multiple branches and I want to clone/pull their branch master (this is not a problem), let's say into the branch "original" (not master). Then, if what I get is compilable, I want to merge with my changes in the local branch named "dev". When I get something compilable in dev, I want to merge into my local "master". At any time, I want to push my branches dev and18:27
master (if possible, not original branch) into *another* distant repo. Also, the original repo uses two submodules, and I'd like to keep them in my other branches dev and master, and if it's possible, to not clone them too many times (I think it can track it is the same commit for submodules, so it would keep the submodule directories when changing the current working branch). Is there something wrong in my idea? Can you help me with that? Thanks for your18:27
help.18:27
ygeLN left18:27
hariel joined18:28
moritz Exagone313: which part do you need help with?18:28
monomon[m] joined18:29
sea-gull joined18:29
ygeLN joined18:29
ToBeFree joined18:30
alhariel left18:31
Exagone313 basically what I currently know and use is clone/pull/add/commit/push. I can read more docs about it (also about merging branches) on my side. What I don't know is if I can pull into original the code I fork, work on dev, and push dev/master into another repo of mine (not on github)18:31
duderono_ left18:31
ronny cbreak: checking jsut for the file was perfect, thanks18:31
ronny left18:32
texasmynsted left18:32
vannorden left18:32
jknetl left18:34
emptynine joined18:34
texasmynsted joined18:34
sveinse left18:35
dreiss left18:35
moritz Exagone313: you can add the original repo as a remote, let's say with name upstream18:35
Exagone313: then you can git fetch upstream; git merge upstream/master18:35
cagedwisdom joined18:36
cyan__ joined18:36
eyou left18:37
overo joined18:38
_August_ why would i get a not something we can merge18:39
error?18:39
stuh84 left18:39
cdg left18:40
Groscheri joined18:40
overo hi! Brief question: I'm in branch MyFeatureA. If I 'git add' new updated files for a work-in-progress feature, then I 'git commit' them and then I 'git checkout -b MyFeatureA-experiment', have I committed the new updated files to my new (local) branch MyFeatureA-experiment?18:40
mountpoint left18:40
vuoto left18:40
lungaro minor confusion w/ git config. Is there a wayto use --list w/ a pattern prefix or section?18:41
albel727 left18:41
albel727 joined18:41
Exagone313 so, something like `git remote add -t master upstream url` then when I'm in branch original, `git fetch upstream; git merge upstream/master`. What do I do to set origin only for my dev and master to be able to push? Does original have to be pushed too?18:41
overo or should I had 'git checkout -b newbranch' just before 'git commit' ?18:41
Exagone313 moritz:18:41
nikivi joined18:41
alex1a joined18:41
_August_ nvm i got it18:42
Exagone313 I think it's dumb, just have to push everything to my own distant repo18:46
QwertyDragon joined18:46
mountpoint joined18:47
mountpoint left18:47
athallerathaller_18:48
athaller_athaller__18:48
athaller__athaller____18:48
athaller____athaller18:48
e14 left18:49
mountpoint joined18:49
mountpoint left18:49
abec0 joined18:52
mountpoint joined18:52
mountpoint left18:52
Repox joined18:53
e14 joined18:53
rominronin joined18:54
mountpoint joined18:55
thiago left18:56
crayon joined18:57
crayon left18:57
ronny joined18:58
ronny hi18:58
another question, whats the most reliable poreclain command to figure the current branch?18:58
howdoi left18:59
diogenese left18:59
mablae joined19:00
Rodya_ joined19:00
Repox left19:01
khfeng left19:01
mischat joined19:01
moritz git branch, git status19:03
eivarv left19:03
acetakwas left19:04
jstimm left19:04
davimore_ left19:05
moritz if you meant plumbing, git rev-parse --symbolic-full-name --abbrev-ref HEAD19:06
khfeng joined19:06
eivarv joined19:07
TomyWork left19:07
modlin left19:08
Seveas ronny: and if scripting: do make sure you handle detached heads (== no current branch) properly :)19:09
maret joined19:10
johnnyfive left19:11
converge left19:11
diogenese joined19:11
Overand joined19:11
nilg joined19:12
Overand Is there a reasonable way for me to get "git" to default to a particular remote, i.e. "git clone SomeNonsense" doing "git clone https://github.com/Overand/SomeNonsense" ? (Or allowing 'git clone Overand/SomeNonsense' ?)19:12
ocbtec left19:12
Overand or am I just better off writing a little alias "ghub" that does e.g. "git clone https://github.com/$@19:13
Joel joined19:13
Joel I have two copies of a repository, are there any gui (I know, I know) tools, which will walk them, and graph out the commit history, showing where they intersect and don't?19:13
Overand Ouch! That sounds like a fun problem.19:14
I'm curious what the answers will be19:14
_August_ left19:14
aarobc joined19:14
alex1a left19:14
johnnyfive joined19:15
kadoban Joel: Fetch one into the other and use 'gitk --all' ?19:15
kajnc joined19:15
fuchstronaut joined19:15
star_prone joined19:15
kadoban Overand: I have an SSH alias for github, so I just do 'git clone github:kadoban/whatever' for example.19:15
You can also have rewrite rules on URLs in git, you'd have to look in the config for the syntax though, I don't remember it.19:16
sangy left19:16
PCatinean left19:17
khfeng left19:17
dreiss joined19:17
m0viefreak joined19:19
eivarv left19:19
isysd joined19:20
_ADN_ joined19:20
star_prone left19:20
fuchstronaut left19:20
johnmilton left19:21
thebloggu left19:22
nidr0x joined19:22
Endarked left19:22
[ADN] joined19:22
phaleth left19:25
Endarked joined19:25
_ADN_ left19:25
menip joined19:25
rominronin left19:28
Skryll left19:29
le_melomane joined19:30
skyfaller left19:31
kajnc left19:31
mablae left19:31
artisanIndia left19:32
maret left19:32
crayon joined19:32
crayon left19:32
crayon joined19:32
Endarked left19:34
duderonomy joined19:35
dreiss left19:35
duderonomyGuest3215619:35
zeroed joined19:36
zeroed left19:36
zeroed joined19:36
LocusAsaf left19:38
Haliucinas joined19:38
Haliucinas left19:38
_ikke_ Joel: Easiest is to let git do the work19:38
either add one as a remote to the other, and fetch from it, or create a new repository and fetch both in there19:38
johnmilton joined19:39
menip left19:39
Electrometro left19:41
patarr left19:42
elastix joined19:44
nikivi left19:44
davimore joined19:45
nikivi joined19:46
Joel _ikke_, I'm trying to figure out why I'm getting unexpected behavior19:46
dreiss joined19:46
eivarv joined19:46
nikivi left19:48
overo hey all, I committed a feature to the wrong branch. Is there a way to move the commit onto the right branch?19:48
^7heo not "move" per se no19:48
overo oh I see19:49
^7heo I mean, depends if you pushed19:49
overo I could 1. checkout on the commit 2. push it to the right branch too 3. revert the commit from the wrong branch, maybe?19:49
^7heo nah wait19:49
overo k19:49
^7heo go on the branch where you want the commit19:49
overo k19:49
^7heo cherry-pick it19:50
modlin joined19:50
overo git cherry-pick ? Do I need any other parameter?19:50
ahmedelgabri left19:50
Guest26_ joined19:51
^7heo the sha of the commit19:51
Guest26_ left19:51
^7heo like19:51
git log -n1 --online branch-where-the-commit-is19:51
will show you the sha19:51
or the shorthand19:51
overo oh by the way, it's still in local repo19:51
do I need --online anyway?19:52
^7heo no19:52
overo I now have the sha19:52
^7heo if it's just in local it's gonna be very easy19:52
so19:53
go to the branch where you want it19:53
overo ok19:53
I am on it19:53
^7heo git cherry-pick $sha19:53
then you have the branch as you want, right?19:54
overo uhm, it doesn't autocomplete the sha, is that a bad sign?19:54
^7heo (and we'll clean the other branch right after)19:54
depends on your shell19:54
overo autocompletion shows branches by name19:54
I'm on bash19:54
^7heo I never use bash19:54
I dunno19:54
try19:54
at worse, the cherry pick will complain and abort19:54
overo error: could not apply 306fe52...19:55
indeed :D19:55
^7heo damn19:55
okay19:55
overo oh my19:55
^7heo I'm sorry I do other things19:55
overo now I have the commit in the right branch too, though :D19:55
^7heo ok?19:55
do a `git status` to check all is in order19:55
khfeng joined19:56
overo there are two changes to be committed (green) and one unmerged path (red)19:56
but the new file is being recognized (the one I committed to the wrong branch)19:56
recognized as waiting to be committed, and I'm on the right branch now, I mean19:56
can I 'git commit -m "stuff"'?19:57
converge joined19:57
finalbeta left19:57
^7heo overo: sorry I'm really in a rush19:58
overo okok19:58
finalbeta joined19:58
overo it seems it works though19:58
tyvm19:58
^7heo overo: I gave you the complex instructions, you might have been ok with a merge or rebase19:58
cherry-pick isn't the easiest19:58
cdown left19:58
^7heo but19:58
you want to resolve the delta19:58
overo git-scm.com good for learning?19:58
^7heo and call `git cherry-pick --continue`19:58
yeah I thnink19:58
overo uhmkay, I'll note that down19:58
"resolve the delta, ..."19:59
cdg joined19:59
osse !eek19:59
gitinfo [!eekaconflict] Merge conflicts are a natural part of collaboration. When facing one, *don't panic*. Read "How to resolve conflicts" in man git-merge and http://git-scm.com/book/ch3-2.html#Basic-Merge-Conflicts then carefully go through the conflicts. Picking one side verbatim is not always the right choice! A nice video explaining merge conflicts: https://www.youtube.com/watch?v=zz7NuSCH6II19:59
osse overo: run 'git diff19:59
some parts of the file have <<<< ===== >>>> in them19:59
fix it so it's how it's supposed to be19:59
chrisgeorge_ joined19:59
crose left20:00
chrisgeorge_ left20:00
overo osse: I've committed featureB to branchA, instead of branchB and I wanted to "move" the commit from branchA to branchB20:00
patarr joined20:00
Alienpruts left20:00
Guest32156 left20:01
overo and it worked as suggested by ^7heo !!!20:02
^7heo overo: btw20:03
overo I mean, I don't know if the commit have been moved around, but now the branchA has only featureA, and the branchB has only featureB !20:03
^7heo when you want to remove the commit from the other branch20:03
if it's on the tip of the branch20:03
chrisgeorge left20:03
^7heo git reset --hard HEAD~20:03
if it has commits on top20:03
cdown joined20:03
^7heo git rebase -i $SHA~20:03
_August_ joined20:03
overo HEAD~ is the parent of current HEAD?20:03
^7heo then edit the file and 'drop' the commit you don't want20:03
overo: yes20:03
EvilPeng1 joined20:04
jknetl joined20:04
TomyLobo joined20:04
ronny Seveas: bascially i want to know the branch im on, and its ok to assume master in case of detached20:04
Ryanar left20:04
Seveas ronny: git symbolic-ref HEAD 2>/dev/null || echo 'master'20:06
EvilPenguin left20:06
rendar left20:06
fb| 20:06
overo left20:07
[Brain] left20:08
IrishPrime left20:08
cdown left20:10
jstimm joined20:10
ExoUNX left20:12
catsup left20:13
Ryanar joined20:14
shaggycat left20:15
nikivi joined20:16
nilez left20:16
fuchstronaut joined20:16
danimal2 left20:17
thiefg left20:18
aarobc left20:19
nilez joined20:19
Groscheri left20:19
SteffanW left20:21
styx_ left20:21
Groscheri joined20:23
dsteplight__ joined20:24
rominronin joined20:25
dsdeiz left20:26
rnsanchez left20:27
modlin left20:27
nilez left20:27
nilez joined20:27
Balliad joined20:27
dbkaplun joined20:28
dbkaplun i have a long list of files that were once checked in but are now removed/renamed. how do i find what commit removed/renamed them?20:28
star_prone joined20:28
davimore_ joined20:29
pumafied left20:29
_ikke_ git log --diff-filter=D --all <file>20:30
nikivi left20:30
elastix left20:30
khfeng left20:30
iosnerd_ joined20:31
davimore left20:32
iosnerd left20:33
hashpuppy joined20:33
jjasinski left20:33
yohnnyjoe left20:35
khfeng joined20:36
thiago joined20:36
patarr left20:37
le_melomane left20:37
garzer joined20:38
fuchstronaut left20:39
aarobc joined20:39
gesker joined20:40
khfeng left20:40
heroux left20:41
oskarkv left20:42
heroux joined20:44
Ryanar left20:44
ahr3n joined20:44
scottbuckel left20:44
Rodya_ left20:45
nilez left20:45
nilez joined20:46
Rodya_ joined20:46
patarr joined20:47
zeroed left20:47
Karazhan left20:47
Karazhan joined20:47
davimore__ joined20:48
aafu joined20:49
dbkaplun thanks20:49
EricPoe joined20:49
khfeng joined20:50
Rodya_ left20:50
nidr0x left20:50
gitinfo set mode: +v20:50
davimore_ left20:50
ieee left20:51
aidalgol joined20:51
jast osse: ++ is counted20:52
synthroid left20:53
andlabs joined20:53
andlabs Hi. A few weeks ago my coworker changed some lines in a file, and those changed lines don't show up in my local branch. But git doesn't think they changed, so pushing my own changes - even to that file - don't overwrite those older changes, and a fresh clone reveals the correct lines. What's going on?20:54
dodobrain joined20:54
moritz andlabs: maybe your coworker didn't push his changes? or to a different branch?20:55
andlabs ...and suddenly they show up NOW20:58
I have no idea; sorry for the noise20:58
overlord_tm left20:59
rominronin left20:59
moritz left21:00
LeBlaaanc joined21:00
ilbot3 left21:00
CussBot left21:01
overlord_tm joined21:02
eindoofus left21:03
JamesBaxter left21:03
f3r70rr35f left21:03
garzer left21:04
moritz joined21:04
aarobc left21:04
elijah joined21:05
nilez left21:05
nilez joined21:05
Balliad left21:05
dsdeiz joined21:06
sea-gull left21:07
e14 left21:08
EvilPeng1 left21:10
CussBot joined21:10
MrWoohoo left21:10
EvilPeng1 joined21:10
ilbot3 joined21:10
cyan__ left21:11
khfeng left21:11
nowhereman left21:11
jknetl left21:15
overlord_tm left21:15
mrwat left21:15
khfeng joined21:15
overlord_tm joined21:16
eivarv left21:16
anonymuse left21:16
anonymuse joined21:16
aafu left21:16
overlord_tm left21:17
overlord_tm joined21:17
ayjay_t left21:18
overlord_tm left21:18
garzer joined21:18
ayjay_t joined21:18
overlord_tm joined21:19
yohnnyjoe joined21:19
peterR`` left21:20
anonymuse left21:21
mibr0 left21:22
netj left21:22
netj joined21:23
peterR`` joined21:24
ffffffff11111111 joined21:24
nwkj86 joined21:25
LeBlaaanc left21:25
ash_workz left21:26
Karazhan left21:26
Karazhan joined21:26
HoierM joined21:27
dendazen left21:27
mischat left21:28
mischat joined21:29
AaronMT left21:29
mischat left21:29
GavinMagnus left21:29
mischat joined21:30
gitinfo set mode: +v21:30
mischat left21:30
andlabs left21:30
ffffffff11111111 hi, could you make "make test" honor NO_PERL ? TIA21:30
Darren_ left21:31
EvilPenguin joined21:32
irco left21:33
l4v2 joined21:34
EvilPeng1 left21:34
Erati left21:34
anuxivm joined21:35
e14 joined21:37
overlord_tm left21:40
_ikke_ ffffffff11111111: The !mailing_list is a better revenue for such requests21:41
gitinfo ffffffff11111111: The mailing list can be reached via [email@hidden.address] You don't need to subscribe to the list, you will always be put in cc on reply. Read archives at http://j.mp/gitlist21:41
_August_ left21:41
_ikke_ s/revenue/venue/21:41
manuel left21:41
hahuang61 left21:42
manuel joined21:42
fees left21:42
Seveas ffffffff11111111: no, it cannot.21:43
core test functionality relies on perl21:43
raspado_ left21:45
griffindy left21:45
eshlox left21:46
ffffffff11111111 _ikke_, thank you for info ; I'm patching the test suite ... Seveas, thats not true ; I'm at t5150-request-pull.sh already - it took me a few hours so far and 16 simple patches - "sed" and "tr"; "tac", "xxd" and "dd" on a single occasion each21:46
nezZario joined21:46
gho5t left21:47
ffffffff11111111 I can easily use a few lines of c code utils or "awk" in all cases21:47
raspado joined21:47
NeverDie joined21:47
nezZario Hello gentlemen.. I am wondering, I set my push.default option to 'current'... Why is it still telling me 'There is no tracking information for the current branch...' ? I thought the point of push.default current was that it always pushed/pulled from a branch with the same name on the remote.21:47
xall joined21:48
nezZario That is, if i'm on a branch called 'develop' then I should 'git pull' from the origin/develop and 'git push' to the origin/develop21:48
iosnerd_ left21:49
dmc shouldn't this include git:// https://git-scm.com/book/en/v2/Git-Internals-Transfer-Protocols21:49
EvilPenguin left21:50
Seveas ffffffff11111111: do note that perl is used for constructs where writing portable sed equivalents is not possible (e.g. the ones in test-lib-functions.sh)21:50
misterpink joined21:50
iosnerd joined21:50
Seveas and tac and xxd are not available everywhere and/or portable21:51
raijin joined21:51
nezZario Are we talking about the best portable scripting language? Because there really isn't one.21:52
_ikke_ nezZario: We aren't21:52
littleforest left21:53
nezZario i think perl is probably the most widely distributed language that actually has a tit of power21:53
Seveas nezZario: no, just why some parts of the testsuite rely on perl for portability reasons21:53
nezZario anyone know what's up with the push.default question? i'm just tired of having to --set-upstream-to=....21:53
ffffffff11111111 Seveas, the test suite itself uses "tr" and "sed" - adding "perl" is kind of pointless to me. Using "perl" for the sake of it is kind of sad :). See, "nul_to_q ()" @ "test-lib-functions.sh" uses "perl", a few lines later "q_to_cr ()" uses "tr" - inconsistent in my POV. Anyway, I'll listen to the mailing list advice. 10x for your time21:53
nezZario my git workflow is simple. i want to push/pull one branch at a time with the exact same name on origin21:53
Seveas ffffffff11111111: that's not using it for the sake of it. That one specifically is impossible to do with sed, as not all sed's handle NULL bytes properly21:54
same with handling cr and lf21:54
ffffffff11111111 Seveas, I see your point. I'll try and make a consisten patch. Thank you.21:54
*consistent21:55
NeverDie left21:55
Seveas ffffffff11111111: apparently you don't as you still think it's possible :)21:55
If it were, we would have gotten rid of perl in the testsuite a long time ago21:55
_ikke_ There are smart people working on git21:55
right21:55
Seveas nezZario: current means 'current branch, if and only if it's actually configured with an upstream'21:56
star_prone left21:56
_ikke_ Seveas: That's not clear from the docs at least21:56
EricPoe left21:56
rominronin joined21:56
Seveas it's also wrong. I keep mixing up current and upstream. Sigh :)21:57
elsevero joined21:58
_ikke_ nezZario: It works for me21:59
Electrometro joined21:59
_ikke_ nezZario: https://gist.github.com/Ikke/2efc37dd77af47939e0af5a445fa47c922:00
madewokherd left22:00
ResidentBiscuit left22:00
WayToDoor left22:00
peeps[lappy] left22:00
thebope left22:01
EvilPenguin joined22:01
thebope joined22:01
nowhereman joined22:02
_ikke_ g2g22:02
f3r70rr35f joined22:03
fedepad left22:04
Seveas ffffffff11111111: https://github.com/git/git/commit/f8fc0ee314d0e0c993d2edac8848a4cfe72c771f22:04
e14 left22:04
nikivi joined22:04
yohnnyjoe left22:05
thebope left22:05
ISmithers joined22:06
Dougie187 left22:07
tlab left22:07
patarr left22:08
Groscheri left22:09
ffffffff11111111 _ikke_, I have no doubt there are smart people working on git. Then again, the people who don't make mistakes don't exist yet IMHO as well as the ones who wrote the perfect code that can not be improved. Seveas, I need to complete my patch in order to observe my ignorance. Thank you both for your time. Back to the coding table.22:09
mikecmpbll what'd be the best way to get the tag before last?22:10
ffffffff11111111 left22:10
e14 joined22:11
_cyril_ left22:11
Seveas depends on your definition of 'before' and 'last'22:12
for before: temporally, topologically, or sorted as version numbers.22:12
LionsMane left22:12
Seveas For last: most recent in time, closest reachable from HEAD or maybe something else22:12
mikecmpbll good point. temporally or topologically22:13
kulelu88 left22:13
mikecmpbll the same way that git describe --tags get's the 'latest'22:14
"the most recent tag that is reachable from a commit."22:15
LandonJH joined22:15
Seveas topologically, with actually some changes in more recent gits22:15
jstimm left22:15
Seveas giving side branches less of a priority22:15
jstimm joined22:15
Seveas dodgy hack actually using git-describe: git describe $(git describe | sed -e 's/-[0-9]\+-g[0-9a-f]\+$//')^ | sed -e 's/-[0-9]\+-g[0-9a-f]\+$//'22:17
mikecmpbll cor blimey22:18
converge left22:18
Seveas much less dodgy (yay manpages): git describe --abbrev=0 $(git describe --abbrev=0)^22:18
ochorocho__ left22:18
wgrant joined22:18
afuentes left22:19
safe joined22:19
mikecmpbll Seveas : <3322:20
duh, why didn't i think of that.22:20
Wulf left22:20
nikivi left22:21
chris_ joined22:21
Wulf joined22:22
Darren_ joined22:22
LandonJH left22:22
chris_ left22:23
patarr joined22:23
cagedwisdom left22:23
EvilPenguin left22:24
kulelu88 joined22:26
courrier joined22:27
patarr left22:27
anotheryou_ joined22:30
cdown_ joined22:30
garzer left22:30
mischat joined22:30
einnjo left22:31
rominronin left22:32
codfection joined22:33
kulelu88 left22:33
anotheryou left22:34
courrier left22:34
LucaTM left22:34
codfection left22:35
anuxivm left22:35
khfeng left22:36
mischat left22:36
codfection joined22:36
EricPoe joined22:36
Lor_ joined22:37
HoierM left22:37
yqt left22:37
mizu_no_oto joined22:38
f3r70rr35f left22:38
codfection left22:39
cagedwisdom joined22:39
khfeng joined22:39
garzer joined22:39
boombatower left22:40
codfection joined22:40
madewokherd joined22:41
codfection 122:41
cdown__ joined22:41
malcon left22:42
t-mart joined22:42
nettoweb left22:43
shinnya left22:44
f3r70rr35f joined22:44
cdown_ left22:44
nettoweb joined22:45
Seveas 122:45
theskillwithin joined22:45
kulelu88 joined22:46
khfeng left22:46
Rodya_ joined22:47
mizu_no_oto left22:48
yqt joined22:48
f3r70rr35f left22:49
xall left22:49
andlabs joined22:49
qsx 222:50
cdown_ joined22:50
catsup joined22:51
codfection left22:51
xall joined22:52
cdown____ joined22:52
Rodya_ left22:52
codfection joined22:52
cdown__ left22:53
jstimm left22:53
Limes_ left22:53
nettoweb left22:53
Seveas 322:54
ojacobson π22:54
Seveas fail22:54
cdown_ left22:54
star_prone joined22:57
pumafied joined22:57
King_Hual left22:57
peeps[lappy] joined22:58
pumafied left22:58
heroux left22:59
mikecmpbll left23:00
heroux joined23:00
metrixx_ joined23:01
metrixxGuest9392723:01
star_prone left23:01
dsdeiz left23:01
thebope joined23:02
leeN left23:03
cdown____ left23:04
dodobrain left23:04
dsteplight__ left23:04
Guest93927 left23:05
thiago left23:06
thebope left23:06
theskillwithin left23:06
theskillwithin joined23:07
_cyril_ joined23:08
CEnnis91 left23:08
finalbeta left23:09
ki0 joined23:11
f3r70rr35f joined23:12
_cyril_ left23:12
Eugene kicked Seveas (5)23:14
reim joined23:14
stomplee left23:14
ahr3n left23:14
Eugene changed the topic to: Welcome to #git, the place for git help and public-access television programming | Please take the git survey: https://jk.gs/gsurv | Public logs at http://jk.gs/glog | First visit? Read: http://jk.gs/git | Current stable version: 2.10.1 | Getting "cannot send to channel"? /msg gitinfo .voice | git-bisect: No, not like that. Grow up.23:14
Eugene set mode: -o23:14
garzer left23:16
f3r70rr35f left23:17
themill left23:17
heroux_ joined23:18
heroux left23:18
heroux_heroux23:18
matsaman left23:18
qsx 523:19
themill joined23:20
Mixologic_ left23:21
arescorpio joined23:22
Derperperd joined23:22
bremner suckup23:24
f3r70rr35f joined23:25
dsdeiz joined23:25
BPL left23:26
Shentino left23:26
Mixologic_ joined23:28
Jameser joined23:28
littleforest joined23:29
rominronin joined23:29
Wulf left23:29
duderonomy joined23:29
duderonomyGuest7569723:30
HoierM joined23:30
nezZario Then what in the world did I do ?23:31
Why does everytime I go to push it makes me --set-upstream-to=23:31
LeBlaaanc joined23:31
mischat joined23:32
LeBlaaanc left23:33
Dohplay joined23:35
Jameser left23:36
mischat left23:36
hahuang61 joined23:36
Remram left23:37
mountpoint left23:39
mancha joined23:39
iosnerd left23:39
milki you probaly dont have a goodd default23:39
Guest75697 left23:39
QwertyDragon left23:39
milki git config push.default23:39
Remram joined23:39
mancha hi folks. does "git reset --hard HEAD^" nuke any trace of the last commit? in case it contains sensitive info.23:40
cdown_ joined23:40
mancha and if not, how to purge all traces (in objects etc) of the last commit.23:40
cagedwisdom left23:40
milki mancha: !sensitive can help you23:40
gitinfo mancha: [!filter_sensitive] You can use filter-branch to remove sensitive data from a repository's history. https://help.github.com/articles/remove-sensitive-data/23:40
duderono_ joined23:41
milki mancha: if you havent pushed to a public repo yet, what you did is probably sufficient to ensure you dont push your sensitive commit23:41
mancha: you can folow up with the cleanup steps in the article23:41
hahuang61 left23:42
mancha i've not pushed. i did re-commit which created a file with the same name (without the sensitive info)23:42
dodobrain joined23:42
manuel left23:42
mancha those instructions you link seem to rely on the path of the file to do its cleaning. but filename is re-used. :/23:42
is there an wasy way to troll the caches and objects and show them in human form so i can see if the sensitive data is anywhere locally?23:44
snowkidind joined23:45
nickthetait left23:45
yqt left23:45
duderono_ left23:46
duderono_ joined23:46
mancha oh yeh, i see it there. i found it with reflog. so i guess i need to do some cleaning but not sure how.23:47
Rodya_ joined23:48
ki0 left23:48
jbitdrop left23:50
solrize left23:50
milki mancha: basically you need to remove references to anything that points to the original file before you can force a garbage collection23:50
mancha: you already removed the old commit from your branch, but you also need to cleanup your reflog23:50
mancha right.23:50
how? :)23:50
milki mancha: step 9 shows that23:50
CussBot left23:51
milki mancha: you can skip the for-each-ref since you didnt do the filter-branch steps23:51
l4v2 left23:51
mancha ok, this doesn't work well23:53
because sensitive commit was #523:53
cdg left23:53
mancha if i use the time for that won't it expire reflogs for all <5?23:53
Rodya_ left23:54
milki you are going to expire all reflogs23:55
you might be able to expire a single reflog23:56
um23:56
guess not23:56
milki shrugs23:56
mancha ok23:56
i think the easiest is to save the commits (maybe as patches) and then basically replay the commit process on a new repo.23:57
is there an easy way to replay commits or should i just script this in bash or similar?23:57
milki the alternative to 9 is listed at the end of the step23:57
duderono_ left23:57
milki just clone the repo23:57
mancha that'll be clean of cruft?23:57
CussBot joined23:57
railssmith joined23:57
milki your new repo wont have cruft23:57
mancha ah nice.23:57
milki fresh clones never have cruft23:58
probably23:58
mancha hah23:58
milki you cant clone unreachable objects at least. that would be a security violation23:58
dbkaplun left23:59
milki and clone doesnt use reflogs23:59
mancha let's give it a whirl23:59
milki if you know what your object id was, you can verify its gone in the new clone with git cat-file23:59

Logs Search ←Prev date Next date→ Channels Documentation