IRCloggy #git 2016-08-17

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-08-17

abyx left00:00
cyan__ left00:00
Neico joined00:01
yoan left00:01
oich left00:06
arescorpio joined00:06
qpdb left00:07
qpdb joined00:07
jimi_ left00:07
grant-h left00:09
weckl left00:10
rkazak joined00:11
crayon left00:13
vassagus joined00:14
p4trix left00:14
shgysk8zer0 joined00:15
dreiss left00:16
vassagus left00:18
spudowiar left00:20
eka joined00:21
cyphase left00:21
fstd_ joined00:22
stux joined00:23
fstd left00:23
fstd_fstd00:23
cyphase joined00:26
Lipp joined00:26
JamesBaxter joined00:27
nitric left00:27
xall left00:28
JamesBaxter left00:32
nullp0inter joined00:33
rkazak left00:33
weox left00:34
foist left00:34
tgunr left00:38
RustyShackleford So i'm working on my own feature branch. All developers are in one repository, no forks00:39
this is a rewrite, so lots of initial development. I would like to keep my branch up to date with master, daily perhaps00:39
durham left00:39
RustyShackleford I also back up my work remotely often since I work from another computer00:40
durham joined00:40
RustyShackleford is there a way to do this without needed to force push?00:40
al-damiri left00:40
nedbat RustyShackleford: without a force push to where?00:41
RustyShackleford my own feature branch00:41
clemf left00:41
kadoban RustyShackleford: You can merge master into your branch occasionally.00:41
nedbat RustyShackleford: you could merge master into your branch. why don't you want to force push?00:41
RustyShackleford it makes coworkers uncomfortable00:41
kadoban Without needing to force push, I think that's really the old way.00:41
harish_ left00:42
kadoban s/old/only/00:42
JamesBaxter joined00:42
RustyShackleford I don't think its risky. Nobody else is using my branch00:42
ahr3n left00:42
RustyShackleford but I'm not sure how common the rebase and force push tactic is00:42
m0viefreak left00:42
kadoban Quite common00:43
nedbat RustyShackleford: i do it all the time.00:44
RustyShackleford: but you do want to be careful that you are the only one using the branch.00:45
xaa left00:47
Sample left00:47
Lipp left00:49
bobdobbs left00:49
nettoweb left00:51
crayon joined00:51
Bizkit left00:54
durham_ joined00:54
tesuji_ joined00:54
danimal2 joined00:55
kulyzu joined00:55
kulyzu left00:55
ytl joined00:55
ShekharReddy joined00:55
kulyzu joined00:55
tesuji left00:55
xall joined00:56
durham left00:56
b1tchcakes left00:57
b1tchcak_ joined00:57
rewt RustyShackleford, why do you need to force push?00:58
Anderson69s_Pi joined01:01
cdg left01:01
pi__ left01:03
eka left01:04
eka joined01:05
xall left01:06
fractalizator_ joined01:06
rossome joined01:07
abyx joined01:07
nunchuck left01:07
ahr3n joined01:08
shgysk8zer0 left01:08
kulyzu left01:09
pks left01:09
fractalizator left01:09
rj11 joined01:10
rj11Guest9701301:10
d^sh left01:10
pks joined01:10
clemf joined01:11
d^sh joined01:11
nedbat rewt: if you rebase your branch, you need to force push01:11
zivester joined01:12
rj1 left01:12
rewt could just merge instead01:13
nullp0inter i have a master and a beta branch, i work out of my home dir, but i want to be able to look at both beta and master on the web...i have two dirs /var/www/html/webapp and /var/www/html/beta how do you set these up to pull from the repo? im going to explore automatic deployment soon, just want to get some previews going01:14
do i clone in there?01:14
vassagus joined01:15
rewt make a script to pull one branch and copy the files over, then pull the other branch and copy the files to the other dir01:15
Guest97013 left01:16
abyx left01:16
rj1 joined01:16
nullp0inter rewt, do i do a git init in those dirs?01:17
RustyShackleford left01:17
rewt no git in those dirs01:17
copy from your git dir to those dirs with cp/scp01:17
abyx joined01:18
RustyShackleford joined01:19
a3Dman left01:20
mingrammer joined01:20
vassagus left01:20
shinnya left01:20
EvilPeng1 left01:20
Orville joined01:22
a3Dman joined01:22
l4v2 joined01:24
mingrammer left01:24
theskillwithin left01:33
clarens0000 joined01:34
theskillwithin joined01:35
clarens0000 left01:35
mellernoia left01:38
rchavik joined01:43
dsantiago left01:45
abyx left01:45
b1tchcak_b1tchcakes01:45
ilbot3 left01:46
Lipp joined01:46
theskillwithin left01:47
ilbot3 joined01:48
hahuang61 joined01:50
Darren_ left01:51
Lipp left01:52
crayon left01:52
Vampire0 joined01:53
RustyShackleford so you guys are not against frequent rebase-and-force-pushing?01:54
seems to be a controversial topic01:54
paws_ left01:54
xall joined01:55
hahuang61 left01:55
Vampire0_ left01:56
shaggycat joined01:56
SporkWitch didn't we cover this rather thoroughly last night?01:57
settermjd joined01:57
RustyShackleford SporkWitch, sure. I got different answers when I asked again though01:58
not that I'm saying you're wrong01:58
SporkWitch not a problem, was just wondering why i fell through a time warp01:58
RustyShackleford IIRC you suggest working in my own fork and then rebasing as I please01:58
SporkWitch when i time warp, i like there to be tim curry around01:59
yup!01:59
the history that matters is the history others could potentially see BEFORE the rebase01:59
cyphase left01:59
theskillwithin joined02:00
SporkWitch if it's in a private repo, there's no harm done, the worst case is they see terrible commit comments and you potentially introduce some reversions. It's when others see it before the rebase and again after that problems can crop up, because now we have conflicting history between repos02:00
s/reversions/regressions/02:00
xall left02:01
RustyShackleford but if each developer works in his own branch, all of which branch from master02:01
Shakeel__ joined02:01
RustyShackleford rewriting history shouldn't affect anyone but me02:02
settermjd left02:02
SporkWitch RustyShackleford: fetch grabs 'em all02:02
pothepanda left02:03
Literphor left02:03
RustyShackleford okay good point. So they would potentially run into issues if they check out my branch?02:03
SporkWitch RustyShackleford: more than that02:03
RustyShackleford: check the manpage: man git fetch02:04
gitinfo RustyShackleford: the git-fetch manpage is available at http://jk.gs/git-fetch.html02:04
nullp0inter left02:04
cyphase joined02:04
SporkWitch loves this bot02:04
RustyShackleford nobodies complained about a broken git repo yet02:06
mingrammer joined02:06
RustyShackleford read the manpage. What am I supposed to conclude?02:06
clemf left02:06
SporkWitch and now the reason you've asked three times is clear: you didn't LIKE the answer lol02:08
if you're just looking for the answer you wanted from the start, go into your bathroom, you've got a mirror in there most likely.02:08
the manpage is fairly self explanatory, and explains all of what it pulls. When you rebase and force-push, you're changing that history. Now the history in the repo you pushed to doesn't match the history in anyone else's.02:09
mingrammer left02:09
Rodya_ joined02:09
_sjs left02:10
RustyShackleford SporkWitch, got me there :p02:14
doesn't the next git fetch fix their history issue?02:14
mingrammer joined02:14
Literphor joined02:15
_Cyclone_ left02:15
vassagus joined02:16
SporkWitch RustyShackleford: potentially, or maybe they take something you did to some file because it helps them02:16
shaggycat left02:16
SporkWitch RustyShackleford: end of the day, you're rewriting history in a shared repository, and that is BAD™02:16
RustyShackleford I think I'll get this branch merged in and then start working in a fork just to be safe02:17
SporkWitch that would typically be the best way. storage is cheap.02:17
shaggycat joined02:19
RustyShackleford welp, gonna consult with myself in the bathroom mirror real quick02:19
watabou joined02:19
vassagus left02:20
RustyShackleford managing a fork is a pain in the butt. Not that difficult, but an extra step02:20
SporkWitch it really isn't lol02:21
rwswitch left02:21
rwswitch joined02:22
chachasmooth left02:22
SporkWitch done right it's a grand total of ONE extra step: forking the repository in the first place. After that, your workflow wouldn't actually change or add any steps, but you WOULD be removing the risk of buggering up the history on the shared repo02:23
chachasmooth joined02:24
RustyShackleford i've screwed up by confusing the two repos. Granted, it was my fault for having them both on my computer02:25
both open in a terminal window02:25
nettoweb joined02:26
SporkWitch well, that's a problem with the main repo; it shouldn't even be ALLOWING you to force-push to it, in a sane configuration02:26
RustyShackleford nothing is sane where I work hah02:27
we're all pretty new to git, recent migration. I've used it before, but on my own projects not in a team02:27
SporkWitch but that's about the only thing that would change: you push to origin (which should be your repo, not the one you forked FROM), and you submit pull requests to upstream (the one you forked from)02:27
you don't push upstream, you ask upstream to pull from you; end result is the same, but the agency is different, and that difference is essential for maintaining integrity and preventing issues (like accidentally damaging the upstream because you pushed to the wrong place)02:28
nettoweb left02:29
rwswitch left02:29
rwswitch joined02:29
RustyShackleford do pretty much all git servers allow for pull requests and forks?02:30
github and bitbucket do02:31
SporkWitch RustyShackleford: entirely dependent on the settings of the system02:32
RustyShackleford: github private repos require auth to clone (which is all a fork is, initially; formal "forking" in things like github and bitbucket is merely a tracking tool to maintain the relations and allow for easy visibility and collaboration, within those that are authorized to view it)02:34
nullp0inter joined02:34
hexagoxel left02:35
cdown joined02:35
lagothrix joined02:36
durham joined02:37
lagothri1 left02:39
rads joined02:40
hexagoxel joined02:40
rads left02:41
ahmedelgabri left02:41
durham_ left02:41
tgunr joined02:41
durham left02:41
rwswitch left02:42
atomicb0mb joined02:43
HoierM left02:45
Goplat joined02:46
darkbit joined02:46
moei left02:46
dodobrain joined02:48
moei joined02:48
snowkidind joined02:49
Rodya_ left02:50
skylite left02:50
skylite joined02:51
crayon joined02:53
shaggycat left02:55
NeverDie left02:55
thiago left02:57
dodobrain left02:58
cdown left02:59
Dougie187 left02:59
atomicb0mb left03:00
rwswitch joined03:00
aavrug joined03:00
aavrug left03:01
aavrug joined03:01
aavrug left03:02
dodobrain joined03:02
aavrug joined03:03
madewokherd left03:03
fstd_ joined03:04
NeonSynth left03:06
boombatower joined03:07
cyphase left03:07
dhollinger joined03:07
nullp0inter left03:07
fstd left03:08
fstd_fstd03:08
rossome left03:09
nunchuck joined03:10
kulelu88 left03:12
cyphase joined03:12
JamesBaxter left03:13
b1tchcak_ joined03:14
clemf joined03:14
johnny56 left03:15
vassagus joined03:16
b1tchcakes left03:17
OrvilleWright joined03:20
vassagus left03:21
rossome joined03:21
Orville left03:22
hahuang61 joined03:22
annoymouse joined03:23
Literphor left03:24
mehola joined03:26
Pinkamena_D joined03:26
hahuang61 left03:27
mostlybadfly left03:27
rwswitch left03:28
b1tchcakes joined03:28
b1tchcak_ left03:28
Maple__France03:29
FranceMaple__03:30
b1tchcak_ joined03:31
b1tchcakes left03:32
b1tchcak_ left03:32
mehola left03:35
Literphor joined03:36
xall joined03:38
rgrinberg left03:38
BSaboia left03:40
texinwien_ joined03:41
snowkidind left03:41
JanC_ joined03:42
JanCGuest3379103:43
Guest33791 left03:43
JanC_JanC03:43
danimal2 left03:44
robogoat joined03:44
Maple__ left03:45
rwswitch joined03:45
mehola_ joined03:46
The_Phoenix joined03:47
The_Phoenix left03:47
The_Phoenix joined03:48
The_Phoenix left03:48
Lipp joined03:48
afuentes left03:49
The_Phoenix joined03:49
The_Phoenix left03:50
The_Phoenix joined03:51
diegoviola left03:52
Lipp left03:53
Derperperd left03:54
rwswitch left03:54
tgunr left03:54
rwswitch joined03:55
Derperperd joined03:55
chandu20 joined03:56
scott_sd joined03:56
rwswitch left03:57
clemf left03:57
bayman joined03:58
GT4066 joined03:59
thecomedian left04:00
thecomedian joined04:00
cfxd left04:02
clemf joined04:03
blackwind_123 left04:04
johnny56 joined04:07
Andrew_K joined04:07
netj left04:10
netj joined04:11
dhollinger left04:11
rkazak joined04:14
dsantiago joined04:14
arescorpio left04:15
vassagus joined04:17
_sjs joined04:18
Cabanossi left04:19
jas4711 left04:20
Cabanossi joined04:22
linuxmodder-linuxmodder04:22
_sjs left04:22
vassagus left04:22
snowkidind joined04:24
nettoweb joined04:24
daynaskully left04:26
ljc joined04:27
realz left04:27
Pinkamena_D left04:27
Pinkamena_D joined04:27
realz joined04:30
InfoTest left04:31
xall left04:37
MrWoohoo joined04:38
bayman left04:41
kadoban left04:43
chandu20 left04:44
ljc left04:46
sdothum left04:47
ljc joined04:48
_W_ left04:49
ljc left04:50
kutsuya left04:52
CheckDavid left04:53
dr_lepper joined04:55
Gamecubic left04:55
subhojit777 joined04:57
snowkidind left04:58
xall joined04:59
YourTheBombNow23 joined04:59
cqi joined05:00
eivarv joined05:04
kutsuya joined05:06
tjayanth joined05:07
Kaisyu left05:07
Lipp joined05:10
eivarv left05:13
nunchuck left05:16
Lipp left05:16
diogenese left05:18
ShekharReddy left05:19
vassagus joined05:20
chandu20 joined05:21
Khisanth left05:22
aidalgol left05:23
hahuang61 joined05:23
chachasmooth left05:24
vassagus left05:25
nunchuck joined05:25
leeN joined05:26
dr_lepper left05:27
hahuang61 left05:28
jrobeson joined05:28
Kaisyu joined05:28
chachasmooth joined05:30
zivester left05:31
OrvilleWright left05:33
diogenese joined05:33
Khisanth joined05:34
jrobeson left05:35
thiago joined05:36
nunchuck left05:36
chandu20 left05:37
nidr0x joined05:38
nettoweb left05:38
zeroed joined05:39
circ-user-RNfpp joined05:40
GT4066 left05:44
tyreld left05:45
govg left05:45
clemf left05:47
mariuscc joined05:49
eivarv joined05:49
eivarv left05:51
Raging_Hog joined05:52
Manuel15 left05:54
nunchuck joined05:54
_sjs joined05:56
bocaneri joined05:56
settermjd joined05:57
mehola_ left05:58
Manuel15 joined05:58
Manuel15 left05:58
Manuel15 joined05:58
rscata joined05:59
kappy joined06:00
LucaTM joined06:03
satya4ever joined06:03
dodobrain left06:03
Pinkamena_D left06:03
YourTheBombNow23 left06:04
dodobrain joined06:05
TomyLobo joined06:07
tgunr joined06:09
tgunr left06:09
jceb joined06:10
tgunr joined06:12
roelmonnens joined06:13
rkazak left06:14
mehola joined06:16
tgunr left06:17
tgunr joined06:19
ahr3n left06:20
govg joined06:20
vassagus joined06:21
tgunr left06:25
tgunr joined06:25
vassagus left06:26
alansaul joined06:26
kugel_kugel06:27
l4v2 left06:28
qt-x joined06:28
Lipp joined06:34
jknetl joined06:34
tgunr left06:36
TomyLobo left06:37
th3Dotor joined06:37
freimatz joined06:38
Lipp left06:38
Jibz joined06:38
inflames joined06:41
sin3t left06:43
Jibz I'm on Windows, and I've converted a mercurial repo to git (hg-fast-export), and did a rebase to reword most of the commit messages. Now I wish to set the commit date back to the author date, but `git rebase --committer-date-is-author-date --root` appears to set the commit date to now. Anything I am doing wrong?06:43
Sceorem joined06:46
_sjs left06:47
inflames left06:47
Jibz hmm looks like --root implies -i (for no apparent reason), so --committer-date-is-author-date silently does nothing .. sigh06:49
tgunr joined06:50
mingrammer left06:51
thiago left06:53
fractalizator_ left06:53
freddymungo joined06:56
jstein_ joined06:57
submitnine joined06:57
rkazak joined06:58
niranjan left06:59
jstein_jstein06:59
jeffreylevesque_ joined06:59
jeffreylevesque left07:00
RustyShackleford left07:02
niranjan joined07:04
alansaul left07:08
peepsalot left07:08
settermjd left07:08
MainB joined07:09
watabou left07:09
jguillen joined07:13
fahadash left07:13
freimatz left07:13
alansaul joined07:14
chigang_ joined07:15
freddymungo left07:16
freddymungo joined07:16
freddymungo left07:16
nunchuck left07:17
t0by joined07:18
styler2go joined07:18
ome joined07:22
vassagus joined07:22
xaa joined07:22
hahuang61 joined07:24
saedelaere joined07:24
Freeze16 left07:25
th3Dotor left07:26
Balliad joined07:26
vassagus left07:26
ytl left07:27
tgunr left07:27
rkazak left07:28
hahuang61 left07:28
venmx left07:30
vuoto joined07:30
Lomex joined07:30
sddwdw joined07:30
Pulp left07:31
sddwdw How do I remove the latest commit from master?07:31
mingrammer joined07:32
selckin rewrite history so it never happened remove, or revert by commiting the inverse?07:33
Impaloo left07:33
Impaloo joined07:33
mingrammer left07:33
mingrammer joined07:33
Guest93616 left07:36
WAA1H2P joined07:36
Guest93616 joined07:36
ki0_ left07:36
ki0 joined07:37
spudowiar joined07:39
gitinfo set mode: +v07:39
alansaul left07:40
Goplat left07:40
Xin joined07:41
Xin hey all im just getting used to git command line lol07:41
we want to track everyones stuff so we can see who is doing what using git remotes07:41
so we want to do something like a dev comes in to program for the day07:41
ahmedelgabri joined07:42
Xin they clone/fork the current dev branch from a public project07:42
ljc joined07:42
Xin now I have say 10 users with clones/forks...07:42
how do I get all their individual changes into the public dev branch07:43
th3Dotor joined07:43
Xin like what do they do at the end of their sessions?07:43
th3Dotor left07:43
alansaul joined07:43
selckin they go home07:44
Xin lol but how do they merge it in?07:44
and how do I allow them access to do so?07:45
selckin they work on features/changes and create logical commits for those, and when they are ready to get usually get pushed/merged into the central repo07:45
jaafar left07:45
Xin so how do they push that to a public git though without say github07:46
selckin by typing git push07:46
Xin or can I allow them to push to github somehow?07:46
sddwdw left07:46
selckin !github07:46
gitinfo Note that git != github. Feel free to ask us about Github-specific features (Forks, Pull Requests, Wikis, etc), but there are no guarantees. There is a #github channel, which might help too (again, no guarantees)07:46
marcm left07:46
Xin right im asking how to do it without github07:46
-_-07:46
selckin standard feature07:46
notting special07:46
Impaloo !man git-push07:46
gitinfo The git man pages are available online at http://jk.gs/git.html. Or were you looking for the "man git-foo" syntax(without the !) ?07:46
the git-push manpage is available at http://jk.gs/git-push.html07:46
Xin they do something like git push git:git@originhost07:47
right?07:47
selckin !man git-remote07:48
gitinfo The git man pages are available online at http://jk.gs/git.html. Or were you looking for the "man git-foo" syntax(without the !) ?07:48
the git-remote manpage is available at http://jk.gs/git-remote.html07:48
Lipp joined07:51
Xin yep so I add the correct remote origin and branch details07:53
and if they push over ssh then they just need a user account on the server eh?07:53
selckin !gitolite07:54
gitinfo Gitolite is a tool to host git repos on a server. It features fine-grained access control, custom hooks, and can be installed without root. Download: https://github.com/sitaramc/gitolite Docs: http://gitolite.com/gitolite/07:54
selckin but yes07:54
Xin yeah im not sure I need anything like that, this is great07:55
thanks for your advice07:55
nikivi joined07:57
kurkale6ka joined07:57
rchavik_ joined07:57
armin i'm just writing a script to create/delete/list repositories on a remote server accessible via ssh because i got too annyoed by gitolite actually.07:57
shoot me.07:57
selckin gitolite is awesome, you're the problem07:58
KeelOfSteel left07:58
darkbit left07:58
armin selckin: i've actually used it for a long time.07:58
mehola_ joined07:58
jceb left07:58
selckin maybe it doesn't match your usecase, but its still awesome07:58
mehola left07:58
KeelOfSteel joined07:59
sin3t joined07:59
Xin left07:59
EduardoMartins joined07:59
armin selckin: it surely is awesome. that doesn't mean i could implement something like that on my own, though, so let's try. i'm not even saying i won't fail at trying to do so. :)08:00
selckin: i used it. for a long time. probably what annoyed me most was debian's default, but i don't have other distributions or operating systems to compare with.08:01
rchavik_ left08:01
mohabaks joined08:02
dreiss joined08:04
ljc left08:05
alansaul left08:07
TomyWork joined08:07
Oebele joined08:08
ki0_ joined08:11
ki0_ left08:11
ki0_ joined08:11
bongjovi joined08:12
dreiss left08:13
tomog999 joined08:13
ki0 left08:14
sitaram armin: https://paste.fedoraproject.org/409478/14714216 is some ~/.gitconfig aliases I use when even I feel gitolite is too heavy :-)08:14
tomog999_ left08:15
nikivi left08:15
sitaram but honestly, gitolite with a simple wild card rule would be the same end-result, but more flexible if things change later08:15
slugmandrew joined08:16
nikivi joined08:17
Phlogistique left08:17
sitaram armin: what was the "debian default" issue? I'm interested in details (even if I don't use debian)08:17
WayToDoor joined08:17
hjubal joined08:18
crayon left08:20
jceb joined08:21
robotroll joined08:22
infra-red joined08:22
vassagus joined08:23
lynkd joined08:23
Guest93616 left08:25
Guest93616 joined08:25
vassagus left08:27
Virox joined08:29
chll_ joined08:32
fakenerd joined08:34
cqi left08:34
ahmed_elgabri joined08:34
maaarghk joined08:34
jason237 left08:35
maaarghk Hi, quick question - I want to do a sparse checkout of a single folder. Is it possible to effectively chroot the working copy to that single folder?08:36
venmx joined08:36
ams__ joined08:37
maaarghk It would be as if the following were possible; `git checkout https://github.com/git/git/Documentation`08:37
slixpk joined08:37
selckin no08:37
ahmedelgabri left08:37
lb maaarghk sparse checkout? you could play with die env variable GIT_DIR and then do the normal git checkout -- /path/to/folder08:37
selckin checkout or clone?08:38
alansaul joined08:38
lb ahh right, selckin spotted the key question. checkout works only with local clones...08:38
maaarghk sorry08:39
my brain is back to front08:39
i meant as if `git clone https...` were possible08:39
selckin not possible08:40
maaarghk alright08:40
guess ill use symlinks as a workaround08:41
lb maaarghk no that's not possible. you can only clone with the --depth parameter used, to limit the cloned amount of data08:41
man git clone08:41
gitinfo the git-clone manpage is available at http://jk.gs/git-clone.html08:41
maaarghk yeah that's as in depth of history right?08:41
fate_ joined08:41
lb yes08:41
i don't recommend that though ^^08:41
vuoto left08:41
maaarghk yeah it's not what i'm after anyway08:42
lb but that's more my guts feeling. i don't have a technical reason for it08:42
great \o/08:42
!botsnack08:42
gitinfo Om nom nom08:42
Shentino left08:43
roelmonnens left08:44
maaarghk i think i was probably looking for a --relative paramete ron git read-tree08:44
armin sitaram: hi. i found "gitolite3" to be not the user name i would want on a git server as i like simple user- and host-names, so i ended up changing a lot of those defaults for the user-name to be "git". also what's actually happening is just a wrapper that is being called from authorized_keys as command= which reads $SSH_ORIGINAL_COMMAND so i considered i could roll my own.08:45
lb armin there is #gitolite for gitolite specific questions08:48
armin lb: that's quite awesome. i don't have one, though.08:49
cyan__ joined08:49
annoymouse left08:50
roelmonnens joined08:51
WayToDoor left08:53
Guest93616 left08:53
Guest93616 joined08:54
davisonio joined08:54
_sjs joined08:55
Shentino joined08:56
sitaram armin: yeah that maybe a debian default. But I suspect, after you install it, you can simply ignore "gitolite3" and start *using* gitolite on some other userid (most people prefer "git"). Gitolite is designed to allow any Unix user to be used as a "hosting user"08:57
mehola_ left08:57
sitaram (and "designed to allow" sounds grand but it's actually ssh that's doing it so, no credit to me!)08:57
WayToDoor joined08:57
spudowiar left08:58
chll_ left08:58
_sjs left08:59
Lipp left09:03
notebox joined09:05
chll_ joined09:06
eijk_ joined09:06
eijk joined09:06
Anticom joined09:09
eijk_ left09:11
mahendra_ joined09:11
ki0_ left09:11
ki0 joined09:12
ki0 left09:12
ki0 joined09:12
ki0 left09:12
ki0 joined09:13
djb-irc left09:13
fakenerd left09:14
fakenerd joined09:14
fakenerd left09:15
Oebele left09:15
fakenerd joined09:15
Lipp joined09:16
Thorn__ left09:18
Silenced joined09:19
darkbit joined09:19
Silenced left09:21
Silenced joined09:21
Thorn joined09:21
Lipp left09:22
Guest93616 left09:23
Guest93616 joined09:23
vassagus joined09:23
hahuang61 joined09:24
GenZai joined09:25
_W_ joined09:25
sylario joined09:26
jeffreylevesque_ left09:27
vassagus left09:28
Silenced left09:28
bouncy joined09:28
dmpeters63 joined09:29
hahuang61 left09:29
fakenerd left09:30
fakenerd joined09:31
eijk_ joined09:39
dmpeters63 left09:39
mSSM joined09:39
mSSM I have a branch “bar” off of “master” with commits a, b, c; is it possible to move a, b to a new branch “foo”, and have bar now branch off of foo?09:41
Or is that too insane?09:41
eijk left09:43
mSSM (reason: I want to keep c in bar, because I want to keep a PR on github associated with it...)09:44
Rish joined09:45
Rish left09:47
fate_ left09:50
fuchstronaut joined09:55
Guest93616 left09:55
Guest93616 joined09:56
_ikke_ mSSM: rebasing can help with that09:56
!fixup09:56
gitinfo So you lost or broke something or need to otherwise find, fix, or delete commits? Look at http://sethrobertson.github.com/GitFixUm/ for full instructions, or !fixup_hints for the tl;dr. Warning: changing old commits will require you to !rewrite published history!09:56
jast mSSM: you don't actually need to do any moving, because 'branching off' isn't recorded in git09:56
if you create 'foo' and have it point at b, the overall outcome is the same as though you'd created 'bar' based on 'foo' at b09:56
Guest93616 left09:57
jast so basically all you need to do is this: git branch foo b09:58
omegak left09:58
jast all that assumes that you committed in this chronological order: a first, then b, then c09:58
mSSM jast: Ah, that makes sense.09:59
_Patrick_ left10:01
jceb left10:02
rezrov joined10:02
djb-irc joined10:02
djb-irc left10:03
phanimahesh joined10:03
davisonio left10:05
Silenced_v2 joined10:05
Silenced_v2 left10:05
Silenced_v2 joined10:05
ix007 joined10:06
_Patrick_ joined10:07
Manuel15 left10:07
fozniku joined10:08
saedelaere left10:09
xall left10:09
ome left10:10
stamina joined10:12
inflames joined10:13
gechr joined10:14
gechr left10:14
Manuel15 joined10:15
Manuel15 left10:15
Manuel15 joined10:15
mingrammer left10:15
mingrammer joined10:17
ASOLAr joined10:17
boombatower left10:18
aguimaraes1986 joined10:18
jceb joined10:21
cd-rum left10:21
Silenced_v2 left10:21
ASOLAr left10:22
Peuc left10:23
sitaram armin: sorry was called away... to continue... "just a wrapper [that] reads $SSH_ORIGINAL_COMMAND" is kinda missing the point. *Any* access control system can be (modulo how the OS/app/whatever actually wants to see it) thought of as a wrapper that just reads the **request** being made (which is what the SSH_ORIGINAL_COMMAND has)10:23
weckl joined10:23
vassagus joined10:24
phanimahesh left10:25
eijk_ left10:26
Silenced joined10:27
Silenced left10:27
Silenced joined10:27
ifra201 joined10:28
vassagus left10:28
mSSM left10:30
Silenced left10:31
dmpeters63 joined10:32
dmpeters63 left10:33
mingrammer left10:35
ToBeCloud joined10:37
gitinfo set mode: +v10:37
chid left10:39
chid joined10:41
a3Dman left10:45
inflames left10:46
eka left10:47
a3Dman joined10:48
a3Dman left10:49
lizzin joined10:50
eka joined10:50
lizzin ive installed git-lfs and i've tracked the large file, but i still get the large file detected error when i try to push. what might i be missing here?10:51
skylite left10:51
armin sitaram: and the point is?10:52
sitaram: don't get me wrong, i love gitolite. i just consider it way too complex for most my use cases already.10:52
EduardoMartins left10:53
armin sitaram: also i love writing shellscripts.10:53
diogenese left10:54
Andrew_Kadfadf10:54
a3Dman joined10:54
scott_sd left10:54
Thorn__ joined10:55
adfadf left10:55
xall joined10:56
Hounddog joined10:56
Hounddog Good Morning, i need to ignore all files with in a directory but need to have certain directories added... how would i accomplish this? I could show what i require10:57
Thorn left10:57
Lipp joined10:58
ronny joined10:58
ronny hi10:58
i have a branch i want ro resuffle with interactive merge without moving it to the head its relative to at the same time10:58
how would i do that10:58
selckin Hounddog: you can 'include' with '!some/path'10:59
mostlybadfly joined10:59
armin sitaram: actually i'm hacking on this since 2 hours now and got a fully working way to create/delete/list repositories from remote already, 100% customizable because i know 100% of the code that i wrote. i think that's fairly great and hope you won't consider this offending or as criticism against gitolite.11:00
shams joined11:00
xall left11:00
diogenese joined11:00
WayToDoor left11:00
Hounddog selckin: ahh that might be something http://pastebin.com/F5WWn8t0 this was what i need but without any files in it11:01
cory_ joined11:01
felowe joined11:01
joseph_arnstein joined11:01
selckin Hounddog: git doesn't track directories11:02
Lipp left11:03
Hounddog selckin: i know but i can add a gitignore in there11:04
selckin i have no idea what you mean anymore11:04
Hounddog inside the directory add .gitignore but ignore everything else11:04
Lipp joined11:04
Lipp left11:04
Hounddog that way i can track the directory11:04
Lipp joined11:05
selckin sure11:05
or you can fix your shit the create the directories it needs on startup11:05
you can force add files that are ignored, so can have any random file in there11:05
Hounddog Well to answer in your rude language, That shit is already setup and i am fixing this shit so people who have not a real clue of git can also use this as easily as possible11:06
j416 there there, calm down children11:06
_sjs joined11:06
ljc joined11:07
j416 ronny: I don't quite understand what you mean11:08
sitaram armin: "and the point is"? Reading the *request* is not even half the deal11:08
j416 ronny: you want to change the ordering of commits, yes?11:08
sitaram armin: are you doing this for a single user? It sounds like it if you've got it done with a few shell scripts in 2 hours. (Or I bow my head in reverence at your superior hacking skills)11:10
peib joined11:10
ronny j416: i havea branch i cant rebase to master without conflict that i need to reorder first11:11
sitaram armin: hmm wait I just noticed "way too complex for my use cases"; never mind11:11
j416 ronny: alright.11:11
ronny also - is there a easy way to split the commits in one branch into 2 distinct branches?11:11
j416 ronny: one question at a time, please11:11
ronny ok, lets go for reorder first11:11
j416 ronny: I have not even understood your first question yet.11:11
przemoc left11:12
_sjs left11:12
armin sitaram: actually, yes. for a single user. exactly. my use case is: i have ssh access to some host. i want to host git repositories on that host easily. i'm eventually not root there. just store my damn git repos.11:12
boombatower joined11:12
sitaram armin: for that, I use 3 "~/.gitconfig" aliases. I pasted a link to a pastebin sometime ago. I'm pretty sure they do most of what you want :)11:13
armin sitaram: would you mind grabbing me a link to it?11:14
sitaram armin: https://paste.fedoraproject.org/409512/4714324311:14
(just fpaste-d again; not the same link as before but same content)11:14
armin sitaram: almost what i came up with...11:14
sitaram I kinda guessed :)11:15
ronny j416: i have a branch, that has not been rebased to master, and i want to reorder its commits without rebasing over to master11:16
HoierM joined11:17
cyan__ left11:17
zeroed left11:18
armin sitaram: http://core.m2m.pm/gitctl.txt (beware, work in progress, considered harmful and buggy until proven otherwise)11:18
skylite joined11:19
armin sitaram: basically i was just playing around with that but will probably use that on an every day basis soon probably.11:19
selckin set -e11:20
j416 ronny: just interactively rebase the branch onto a commit earlier in the branch.11:20
mingrammer joined11:20
ronny j416: whats the canonical way to rebase a branch onto its common ancestor with master?11:20
j416 ronny: you can say: git rebase $(git merge-base master HEAD)11:22
(add -i for interactive)11:22
ronny thanks :)11:22
omegak joined11:22
j416 (otherwise this is a no-op)11:22
d0nn1e left11:22
j416 might be able to do it with dot syntax, I always forget so I use the above11:22
d0nn1e joined11:23
zeroed joined11:23
zeroed left11:23
zeroed joined11:23
afuentes joined11:25
vassagus joined11:25
cyan__ joined11:25
cyan__ left11:27
sitaram armin: looks ok on first glance but if it's really meant for yourself it's too verbose. Plus you really need to check/enforce fundamental things like ".git" at the end. And speaking for myself, I never want to delete remotely; it has to be "log on and do it manually"11:27
armin sitaram: good points. thank you!11:27
lizzin left11:28
stamina left11:28
armin sitaram: it's still perfectly valid to do "git init --bare foobar" (without the .git at the end), though. does the ".git" suffix mean something more than "this is a directory that will likely have a .git folder inside"?11:29
vassagus left11:30
jast armin: it means the opposite, actually. convention says that foo.git contains what would normally be inside the '.git' subdir in a normal (non-bare) git repo11:31
sitaram armin: ".git" at the end for bare repos is only a convention but a good one to follow; no hard and fast rules enforced by git itself. Sorry if I made it sound like that11:32
".git folder inside" means it is NOT a bare repo, then it (again, convention) should NOT have a directory name ending in ".git"11:32
or... what jast said (I should have read that before I posted!)11:33
sitaram blames irssi for highlighting messages containing "sitaram" or "gitolite" in red and making me react to them first, in some Pavlovian manner11:33
armin sitaram: you didn't - i'm just trying to understand things. all good. :)11:33
mycyber joined11:34
ronny hmm11:34
anyone aware of a tool that would take a style fixup commit and then integrated it to n previous commits that did the actual changes so that hte result is a style fixed history?11:34
selckin just curious what do you do that has you creating git repos this often?11:34
Sceorem left11:35
selckin ronny: you can use rebase -i to merge fixup commits into older commits or i don't understand what you mean11:36
rwb left11:38
romerocesar left11:38
dsdeiz left11:39
ronny selckin: i have one fixup commit and i want to split it over to 5 older commits since each of the older commits touches different bits that the fixup commit fixes up11:40
selckin you wanna create 5 fixup commits then, (git add -p ) is big help11:41
or manual edit11:41
armin selckin: did that question relate to me?11:46
selckin yeah11:47
ronny selckin: the commit is already done now i want to automatically split it11:47
peib left11:47
selckin ronny: pick edit, unstage, and use git add -p to stage the hunks how you want to split them and commit each part11:47
armin selckin: since you consider the problem to be myself, my motivation to answer this in an honest way is quite low, but i'll try: i like to enhance my knowledge and am bored at work and script things just for fun.11:48
G1eb joined11:49
selckin armin: i don't consider anything a problem, just can't think of a reason where this would be needed, and you don't need it so i wasn't that wrong, but learning is always a good excuse11:49
G1eb heya, I've accidentally removed a file, how do I put it back with git?11:49
I've tried git reset HEAD <file> but that does not do anything11:50
selckin G1eb: git checkout <sha> -- file11:50
G1eb ah, yes thats it11:50
thanks! :)11:50
G1eb left11:50
selckin G1eb: the reset will unstage it, and he left already11:51
Lipp left11:51
jast ronny: I don't think you can do this automatically :(11:51
ronny sometimes i wish i could just drag&drop comits/hunks in a ui11:51
selckin ronny: git gui11:52
ronny selckin: can that drag&drop patch hunks/commits?11:52
jast not exactly, from what I recall11:52
selckin you can stage hunks in the gui then commit11:52
then rebase and merge11:52
jast actually in this specific case a magic special rebase with -Xours (or something?) might work11:53
armin selckin: 09:58:03 selckin gitolite is awesome, you're the problem11:53
jast but that would be a rather special way of doing it :)11:53
armin well...11:53
selckin armin: don't take everything so seriously, you bashed it for a bullshit reason so i countered with that11:54
fuchstronaut left11:54
sdothum joined11:55
jast maybe I missed something, but the annoyance seems to be with debian's defaults for gitolite and not gitolite itself?11:55
selckin at taht point he just said he got "too annoyed" by it11:56
jast if so, I can empathize with that. I've often been dissatisfied with how git-related packages are handled in debian11:56
subhojit777 Is there any way to bypass resolve conflict using mergetool for specific files. My case - I usually get merge conflicts for compiled + minified CSS files, without resoolving the conflict I can easily autogenerate the CSS by running compass.11:56
Seveas subhojit777: don't commit the generated files.11:57
selckin subhojit777: in general you don't commit those files11:57
synthroid joined11:57
jast subhojit777: there are attributes you can set on files to customize how merging is handled, see man gitattributes11:58
gitinfo subhojit777: the gitattributes manpage is available at http://jk.gs/gitattributes.html11:58
jast also, what the other people said :)11:58
subhojit777 Thanks, I will try to suggest this to my superior. But, is there any other way? Like I will manually mark those files as resolved.11:58
bartosz_ joined11:58
selckin what jast said11:59
subhojit777 jast, "other people"? sorry didn't get you? do you mean Google for the problem?12:00
selckin line above that12:00
jast no, I meant the responsess from selckin and Seveas :)12:01
subhojit777 ohkk.. Thanks :)12:01
styler2go Hello. I have a problem with git. My git project is on a samba drive and i laways have file permission differences and thus all files are marked as changed. config.fileMode false did not help. any idea?12:02
johnmilton left12:02
notebox left12:03
selckin samba confnig issue12:04
Sceorem joined12:06
jast it's core.fileMode, actually :)12:06
saedelaere joined12:06
Seveas styler2go: don't pubt repos on samba drives.12:06
selckin you can configure samba not todo that12:06
MyDuckIsGoingMad left12:06
styler2go hmm.. couldn't find any option in samba12:06
jast: yes, tried that12:06
selckin enable unix extensions or disable something or the other, been a few years12:07
i'm sure google knows12:07
ASOLAr joined12:08
jast of course UNIX extensions don't help if the share is accessed by windows clients12:09
selckin can do it with that too12:10
ASOLAr left12:10
selckin *without12:10
jast you can tell your client to disable +x flags for all files, then you'll only run into trouble for files that are *supposed* to be executable :)12:10
styler2go hmm12:11
Maple__ joined12:11
styler2go it always says old 0755 and new 064412:11
YourTheBombNow23 joined12:12
ronny hmm12:12
got cola seems halfway there12:13
styler2go tried a lot of things now... nothign worked sadly12:13
ljc left12:13
YourTheBombNow23 left12:13
snowkidind joined12:14
nettoweb joined12:14
alansaul left12:15
rwb joined12:16
garethdaine joined12:16
Diabolik left12:18
Diabolik joined12:19
Diabolik left12:19
Lipp joined12:19
Diabolik joined12:19
Diabolik left12:19
Diabolik joined12:20
Diabolik left12:20
Diabolik joined12:20
shams left12:20
hahuang61 joined12:22
johnmilton joined12:22
dsdeiz joined12:22
hahuang65 left12:23
jguillen left12:26
fees joined12:26
vassagus joined12:26
The_Phoenix left12:27
johnmilton left12:27
tvw joined12:27
jimi_ joined12:28
The_Phoenix joined12:29
Pinkamena_D joined12:29
aavrug left12:29
mycyber left12:30
vassagus left12:31
kim_bruning joined12:32
shams joined12:32
johnny56 left12:32
TooLmaN joined12:33
johnny56_ joined12:33
kim_bruning Hello, so once upon a time I was clever, and decided to do git init in some of my /etc subdirs (like /etc/asterisk and /etc/samba). Today, I am cleverer, and realize I really would like to just have all of /etc in git ;-) Other than deleting my old git history, what's a smart way to git init in /etc, and include subdirs properly?12:33
tobiasvl that sounds like a strange idea12:34
selckin !etc12:34
gitinfo [!fetch] When you work with remote repositories, Git stores copies of the remote's branches in !tracking_branches (basically mirrors). You can use 'git fetch' to update those. If you want to actually apply changes from the remote to your checked out branch, a second step is needed, usually 'git merge' or 'git rebase'. There's also 'git pull' which combines both steps.12:34
selckin wrong one12:34
!etckeeper12:35
gitinfo etckeeper is a collection of tools to let /etc be stored in a git, mercurial, darcs, or bzr repository. It hooks into various package managers. http://etckeeper.branchable.com12:35
tobiasvl well there you go12:35
you learn something every day12:35
zivester joined12:35
selckin !subtree12:36
gitinfo The subtree merge method is great for incorporating a subsidiary git repo into your current one with "unified" history. Read http://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging#_subtree_merge for more info, see also !git-subtree and !git-stitch-repo.12:36
kim_bruning tobiasvl: keeping /etc in git is sheer genius I tell you.12:36
tobiasvl apparently!12:36
kim_bruning selckin : is git going to be confuzzeled because the ostensible subtree is a subdir of the new repo?12:37
also worried about git add *12:38
Gianormagantrous left12:38
tvw left12:38
kim_bruning scratches head12:38
tvw joined12:38
selckin not sure what you mean, can't do much wrong tho12:38
kim_bruning well, okay then12:39
Hko joined12:39
kim_bruning I should probably practice on something none-etc on none-production first :-P12:39
ShekharReddy joined12:39
kim_bruning Oh! And I should really have the main repo for etc on my backup box (so I can git push and have a sort of backup already)12:40
lynkd left12:40
johnmilton joined12:40
vaibhavsagar joined12:41
selckin need a backup for the rest of the system anyway that includes /etc, the git is just nice for history12:41
gitinfo set mode: +v12:42
vaibhavsagar hi, can anyone explain how to convert an integer into the offset encoded representation?12:42
bremner uhm. Connection with git?12:42
kim_bruning selckin: ofcourse. this way just means more granular backups for that particular dir12:42
vaibhavsagar I can parse it just fine, but I don't understand how to serialize it12:42
bremner: https://github.com/git/git/blob/master/Documentation/technical/pack-format.txt#L119-L12412:43
kim_bruning selckin: *in addition to* the regular ;-)12:43
mycyber joined12:43
bremner vaibhavsagar: oh, ok.12:43
vaibhavsagar: you might need to try the list for internals questions12:43
f0rblaze joined12:43
vaibhavsagar sure, thanks bremner12:44
ToBeCloud left12:45
JamesBaxter joined12:45
vaibhavsagar is that just the git mailing list?12:45
fmcgeough joined12:47
Pinkamena_D left12:47
notebox joined12:48
jimi_ left12:49
davisonio joined12:50
sanketdg joined12:50
m0viefreak joined12:51
CuriousMind joined12:52
kim_bruning ok so to simulate my fun situation I made a dir test and a dir test/foo.d , I did git init in test/foo.d , then git init in test ... so far so bad ( I now have 2 different logs ;-) )12:52
rkazak joined12:52
kim_bruning let's see if I can do the merge12:52
CheckDavid joined12:53
CuriousMind My question is, if I have more than one remote, will git or whatever push my work to both repos? I'm trying to deploy my app on heroku http://xomf.com/cmzlx12:53
That's a screenie of the remotes I have12:54
kim_bruning $ git read-tree --prefix=foo.d/ -u foo fatal: Not a valid object name foo12:54
rkazak left12:54
kim_bruning ok, clearly I actually need to grok what I'm doing ... magical invocations won't work without that ^^;;12:54
SporkWitch CuriousMind: you can script it, but no, normally you push to one at a time12:55
Lipp left12:55
Shentino left12:55
selckin CuriousMind: if ust do 'git push' it will push to the remote tracking branch (not sure if you can have multiple), but you can always push explicitly to both git push origin; git push heroku;12:55
CuriousMind ohh that's how I would do that12:56
kpease left12:57
CuriousMind Oh right you push to one at a time, that makes sense12:57
Ok so I could still push to heroku, I would have to do I don't know "git push heroku master"?12:57
selckin sure12:57
jknetl left12:58
netj left12:58
netj joined12:58
MadHatter42 joined12:58
m1dnight1m1dnight12:59
Pinkamena_D joined12:59
kim_bruning ok, you know what... I don't think I have too many commits in the /etc subdirs... I'm just gonna cp -a out those subdirs just in case, and then apply etckeeper13:00
SporkWitch selckin: you can't (re: tracking multiple). Though some tools will cheat and do it anyway, to show your relative position to your listed remotes13:00
dodobrain left13:00
chid_ joined13:00
kim_bruning selckin: neat that etckeeper is in the debian repo! :-)13:00
garethdaine left13:01
m1dnight_ left13:01
m1dnight_ joined13:01
MadHatter42 left13:02
bsanford left13:02
CuriousMind Thanks SporkWitch selckin13:03
I'm trying to deploy my app to heroku13:03
armin kim_bruning: best thing is that it actually works out of the box, with apt-integration.13:03
MadHatter42 joined13:03
SporkWitch etckeeper?13:04
selckin yeah commits after upgrades etc13:04
albel727 left13:04
pcre_ joined13:04
alansaul joined13:04
talin hello. i need to compare two files on different branches and in different dirs13:07
i tried git diff branch1:file branch2:file, but it claims that it can't find the first file13:07
polyzen talin, try omitting branch1:13:08
garethdaine joined13:09
cdg joined13:09
cdg left13:09
polyzen by the lack of a response, I can only assume Git has crashed your system13:10
cdg joined13:10
ASOLAr joined13:10
Raging_Hog left13:10
talin no such path in the working tree13:11
if i add -- between them, i get some output13:12
not sure if it's correct13:12
CuriousMind left13:13
cyan__ joined13:13
rahtgaz joined13:13
nikivi left13:13
Peuc joined13:13
ASOLAr left13:15
RustyShackleford joined13:15
darkbit left13:16
ws2k3 left13:17
Gitzilla left13:17
bsanford joined13:18
SporkWitch selckin: ok, that tool sounds pretty sweet lol13:18
_sjs joined13:18
al-damiri joined13:19
jstein Hi, I read a discussion about version tagging recently, but do not understand what changed in git in the past. https://github.com/smxi/inxi/issues/92 Do you know, what was bad about tags in the past and changed?13:20
fahadash joined13:21
zeroed left13:21
mingrammer left13:21
rgrinberg joined13:21
ws2k3 joined13:22
_sjs left13:23
kim_bruning is etckeeper init supposed to be slow?13:24
stux|away joined13:25
kim_bruning and git status?13:25
oh boy13:25
zeroed joined13:26
zeroed left13:26
zeroed joined13:26
vassagus joined13:27
jast kim_bruning: with huge directories it can be, though if you have enough RAM the filesystem cache should be able to take the edge off it after the first time13:27
netj left13:27
netj joined13:27
jstein kim_bruning: no, it should not be slow. How long did it take?13:27
kim_bruning 45 megs13:27
I stopped it after a minute13:27
jast you have to keep in mind that 'git status' has to look at the metadata of every single file in the directory13:27
kim_bruning suspect a symlink loop or something13:28
aguimaraes1986 left13:28
kim_bruning ok, there be a lot of files in that dir ;-)13:28
jast the size of the files shouldn't matter as much. if anything, the number of files does.13:28
kim_bruning 779813:28
ExoUNX joined13:28
kim_bruning can't be that bad13:28
jast still shouldn't take a minute unless you've got a tape recorder as your storage system13:28
jstein kim_bruning: that is a lot, but no problem for git13:28
jast or I/O saturation from unrelated processes13:29
(especially if it's not an SSD)13:29
kim_bruning hum, running etckeeper init twice is probably the wrong move :-P13:29
got an ssd and 8 gigs of ram. Not fastest, but definitely not slowest :-P13:30
anyway, this time it was near-instant13:30
selckin time for a backup, your ssd is about to die13:30
kim_bruning apparantly apt-get had run etckeeper init for me already13:30
Ok, let's set up for a remote push13:30
vassagus left13:31
MadHatter42 left13:32
ash_workz joined13:32
zivester left13:33
kim_bruning ok, let's push this thing13:35
mycyber left13:36
sangy joined13:36
kaldoran joined13:36
rossome left13:37
romerocesar joined13:39
kadoban joined13:39
satya4ever left13:39
Shentino joined13:41
kim_bruning hum, for some reason git doesn't accept a remote like ssh://rbackup@pi:myserver-backup13:42
it has to be ssh://rbackup@pi/home/rbackup/myserver-backup13:42
am i Doing It Wrong(tm) ?13:43
ASOLAr joined13:43
romerocesar left13:43
kim_bruning also, now I'm doing git push backup .... but wasn't there a way to make a default for git push13:44
kadoban kim_bruning: I always specify SSH URLs as just me@whatever:/some/path usually leaving off the me@ part as well, since I set that stuff in the alias config in SSH13:44
Muzer left13:44
jeffreylevesque joined13:45
mycyber joined13:45
cqi joined13:45
fairuz joined13:45
shams left13:46
mostlybadfly left13:47
shams joined13:48
ASOLAr left13:48
AaronMT joined13:50
AaronMT left13:51
AaronMT joined13:51
mycyber left13:51
jimi_ joined13:52
macivy joined13:52
kim_bruning ohhhhh, etckeeper immediately runs after I do an apt run13:53
<3<3<313:53
selckin: that was a really neat tip. Why doesn't everyone know about this?13:53
selckin because nutella is to breakfast food13:54
kim_bruning it just doesn't automatically do a push... though that might actually be a Good Thing (tm)13:54
jast kim_bruning: you may be getting the two different SSH URI schemes mixed up. one is user@host:relative/path. the other is ssh://user@host/absolute/path.13:54
kim_bruning jast: indeed!13:55
bsanford left13:55
kim_bruning both are valid for git?13:55
jast yes13:55
TooLmaN left13:56
kim_bruning learn something new every day13:56
jast in fact possibly git even allows ssh://foo@bar/~/relative/to/homedirt13:56
kim_bruning this is why you gotta *do* stuff, RTFM might be necessary, but not sufficient13:56
roflincopter joined13:56
garethdaine left13:56
kim_bruning so now that I've thoroughly shaved this yak, I'm off to shave the next one ;-)13:58
geeze it's 4 pm already13:58
roflin left13:59
Rodya_ joined13:59
nikivi joined13:59
stux left13:59
jaafar joined14:00
roflin joined14:02
fairuzfairuz214:02
fairuz2 left14:04
roflincopter left14:04
subhojit777 left14:04
mingrammer joined14:06
TomyWork left14:06
GodGinrai joined14:06
ncd|leeN joined14:06
phaleth joined14:07
kim_bruning laters o/14:07
kim_bruning left14:08
Finnoloid joined14:08
leeN left14:10
delboy1978uk joined14:10
MainB_ joined14:10
delboy1978uk whatever_file: needs merge14:10
then i nano it, search for <<<, nothing14:10
no conflicts14:10
so what has broken?14:10
ash_workz left14:11
ResidentBiscuit joined14:11
m0viefreak left14:12
delboy1978uk its cool, think ive fixed it14:13
pioiytr joined14:13
jast there are several possibilities, e.g. file mode conflict, delete/modify conflict14:13
tools like 'git merge' and 'git rebase' tell you, as part of their output, what kind of conflict they detected. unfortunately you can't see that information later on, so it helps to pay attention to the output14:14
delboy1978uk jast: interesting, thanks, i'll investigate a little more14:14
garethdaine joined14:14
sanketdg left14:15
sanketdg joined14:16
sanketdg left14:16
sanketdg joined14:17
qt-x left14:19
mattsl left14:19
hahuang65 joined14:20
rgrinberg left14:21
Dougie187 joined14:21
rgrinberg joined14:21
rgrinberg left14:21
l4v2 joined14:22
rgrinberg joined14:22
notfrosty joined14:22
Darren_ joined14:23
hahuang61 left14:23
notfrosty How do I set master up to date from branch without actually changing branch ?14:23
GodGinrai so you want to merge your branch into master14:25
but not change branch?14:25
Literphor left14:25
GodGinrai to reword: but not switch branches?14:25
Manuel15 left14:26
notfrosty No, I wanna see what changes were done in master without switching to it. (git diff --name-status master..branch)14:26
selckin think you might mean like, git fetch; git diff master..origin/master, else i'm lost14:27
delboy1978uk left14:27
GodGinrai ^ this14:27
zivester joined14:27
fakenerd left14:27
cqi left14:27
vassagus joined14:27
madewokherd joined14:28
notfrosty git fetch doesn't update master (git log master doesn't show latest commits)14:28
I wanna do git branch master; git pull origin master; git branch branch; Is it possible without actually changing branch ?14:29
osse notfrosty: fetch updates origin/master14:29
Manuel15 joined14:30
Manuel15 left14:30
Manuel15 joined14:30
przemoc joined14:30
przemoc left14:30
przemoc joined14:30
selckin not in a sane way and only if its a fast forward14:30
osse notfrosty: sort of. you can "push" to the current repo. but it's a bit awkward14:30
use origin/master in place of master. it probably gives you want to want14:30
chigang_ left14:31
stamina joined14:31
GodGinrai notfrosty: it updates origin/master14:32
vassagus left14:32
GodGinrai notfrosty: it would be better to stash, checkout master, pull, checkout branch, and then stash pop14:32
notfrosty ok I got it, thx guys14:33
GodGinrai if you want to update master and be back on your branch14:33
ash_workz joined14:33
osse git push . origin/master:master14:33
aww yiss14:33
lmat When I clone a remote14:34
notfrosty left14:34
lmat I clone a remote (git clone git4 git4clone;) and the new repo's branches don't match the old! :o14:34
eric97477 joined14:35
lmat The old repo had a branch pointing to a particular merge point, but in the new one, that branch is pointing somewhere else!!14:35
This seems very bad.14:35
ncd|leeN left14:35
lmat What's the difference between a green ref and a red ref in git log --decorate?14:35
bremner also somewhat unlikely,14:35
MainB_ left14:36
osse lmat: usually local vs remote branches14:36
kaldoran_ joined14:36
_sjs joined14:36
lmat osse: okay14:36
kaldoran left14:36
Electrometro left14:37
lmat Maybe the problem is how I Get those branches in the original repo.14:38
ikmaak left14:38
lmat I use for remote in $(git branch -r); do git branch --track "$remote"; done;14:38
osse then you clone the original branches become remote branches in the new clone14:38
lmat Does this make all local tracking branches track at HEAD?14:38
clemf joined14:39
osse lmat: i suggest you only create the local branches you need. otherwise it just becomes a mess14:39
lmat osse: No-can-do. I'm converting a repo and I need to get all the branches.14:39
vassagus joined14:39
osse maybe you want clone --mirror then14:39
lmat osse: This will be a "central" repo. Of course, my local14:39
thiago_ joined14:39
lmat HAH!14:39
lmat kisses osse14:40
lmat I'm pretty sure that's the one. Thanks!14:40
submitnine left14:41
lmat osse: Tell me about no-hardlinks. What happens whet I don't pass this?14:41
Darren_ left14:41
osse git hardlinks14:42
lmat osse: so du . -sh;14:42
What is the point of passing no-hardlinks?14:42
rgrinberg left14:43
ifra201 left14:43
lmat *with* hardlinks, du . -sh; shows the total repo size.14:43
osse "This may be desirable if you are trying to make a back-up of your repository."14:44
lmat osse: hmm, okay. Thanks!14:44
osse i don't know more than that14:45
gitinfo set mode: +v14:45
rgrinberg joined14:45
osse and I would guess du counts the size of hard linked files14:45
du can't tell which is the "original" and which is the "linked" files, since that distinction is not present with hardlinking14:46
(i think)14:46
lmat My thoughts exactly.14:46
Tobarja joined14:46
ShekharReddy left14:49
eric97477 I am not sure how to solve this problem. I need to transition two git repos ( X & Y ) from server A to B. I did a git clone —mirror from A and a git push —mirror to B. This all seemed to work correctly and without issue. However, repo X has many branches and repo Y is a submodule on every branch. As I understand it, the .gitmodules file for X is tracked per branch. So, what is the best way to update the location of the submodule Y across all branches in X?14:49
Hopefully this makes sense. I am hoping that I do not need to individually checkout each branch, update the location of the submodule, and then commit/push .gitmodules.14:49
Lipp joined14:50
astrofog joined14:50
TomyLobo joined14:51
nettoweb left14:52
dmto joined14:52
infra-red left14:55
ToxicFrog eric97477: git filter-branch?14:55
robotroll left14:55
bsanford joined14:56
tvw left14:56
eric97477 I honestly have no idea ToxicFrog. I have to assume someone has faced this issue before and I am hoping someone has an easy solution.14:56
artemisart joined14:57
darkbit joined14:57
rscata left14:57
RustyShackleford left14:57
ToxicFrog eric97477: so, the two approaches that immediately come to mind for me are to use filter-branch (if you want to rewrite the historical contents of .gitmodules) or just a simple for loop over the output of 'git branch' (if you just want to make new commits updating it without changing the historical values)14:57
peepsalot joined14:58
suchness joined14:59
eric97477 ok. so, essentially, I need to write a little script that will do the checkout for each branch, modify .gitmodules, and then push the results? I think I like that option better then rewriting history.14:59
suchness Can someone tell me what this means: warning: symbolic ref is dangling: refs/remotes/origin/HEAD14:59
It's been reporting that when i switch branches14:59
selckin !dangl14:59
gitinfo [!dangling] Dangling objects represent things added to git which are no longer needed based on the git commands you typed in. This can be normal workflow (rebase, reset, add, etc) or errors you made. Typing "!dangling_commit" "!dangling_blob" and "!dangling_tree" into a query to me will get you more information about each type.14:59
lmat suchness: I guess that means HEAD doesn't point to a14:59
nevermind14:59
LionsMane joined14:59
selckin you most likely made a commit on a detached head (maybe)14:59
osse eric97477: hmm, maybe I misunderstand but can't you just copy them over?14:59
lmat suchness: You need to create a *local* branch to track that remote.15:00
osse eric97477: oh.. urls in .gitmodules and that I suppose?15:00
eric97477 osse…yes, the url in the .gitmodules need to change for each branch.15:00
InfoTest joined15:01
eric97477 osse…as ToxicFrog mentioned, I could write a script to do this, but if there is an easier way, without rewriting history (unless that truly is the recommended method in this case), I would be interested to learn what that is.15:02
cagomez joined15:02
eric97477 If I didn’t have 30 some branches to update, this wouldn’t be much of an issue.15:02
osse 30 branches! :O15:03
eric97477 do not ask.15:03
roelmonn_ joined15:03
roelmonnens left15:03
osse move repo X first. wait for the whole thing to blow over. forget about moving Y. profit.15:03
eric97477 osse….I like your plan. Sadly, it is not one I can follow. So, a script it shall be.15:04
Guest5 joined15:04
ToxicFrog eric97477: the script seems pretty easy -- for branch in $(git branch); do git checkout $branch; sed -Ei '...' .gitmodules; git commit -am "update repo Y URL"; done15:04
ResidentBiscuit I've never heard of a good story coming out of submodule usage15:04
a_thakur joined15:05
osse eric97477: git for-each-ref --format=%(refname:short) 'refs/heads' | while read branch; do git checkout $branch && sed -i .gitmodules blabla && git commit -am 'Update URL for module'; done15:05
eric97477: e<15:05
$(git branch) :O for i in * master feature; do... Woops!15:06
you rekt yourself15:06
roelmonn_ left15:06
eric97477 thanks. I will go that route and get myself a script to do the work for me.15:06
ASOLAr joined15:07
algae joined15:07
roelmonnens joined15:07
ASOLAr left15:08
JanC_ joined15:08
HoierM left15:08
ToxicFrog osse: if for some reason you have a branch named *, it won't be expanded in the output of $(git branch)15:08
chrisgeorge joined15:08
chrisgeorge left15:09
osse ToxicFrog: git branch prints a '*'. and the shell will expand it15:09
JanCGuest4094615:09
JanC_JanC15:09
osse at least bash/dash/sh will. zsh won't15:09
Guest40946 left15:09
sanketdg left15:10
kaldoran_kaldoran15:10
ToxicFrog osse: aha. That explains it. I tested on zsh.15:11
roelmonnens left15:11
boyen joined15:11
ASOLAr joined15:11
ToxicFrog And totally forgot about the *15:11
suchness left15:12
ASOLAr left15:13
ech0s7 joined15:13
ech0s7 hi!15:13
GodGinrai good morning15:13
Guest5 left15:13
ech0s7 i would create a different patch file for each commit into my repo, one by one in separate file ordered by time (from oldest to newest)15:14
how can i do ?15:14
thiago_ left15:14
cfxd joined15:15
a_thakur left15:15
slugmandrew left15:15
rossome joined15:16
Guest93616 joined15:16
_sjs left15:17
Sceorem left15:17
victorbjelkholm_ left15:17
GodGinrai osse: wouldn't for-each-ref be applicable here? ^15:17
synthroid left15:18
jguillen joined15:18
dhollinger joined15:19
johntramp left15:19
sanketdg joined15:19
tyreld joined15:20
Darren_ joined15:20
mingrammer left15:22
eric97477 left15:22
liamonade joined15:22
Guest5 joined15:22
Seveas ech0s7: man git format-patch15:22
gitinfo ech0s7: the git-format-patch manpage is available at http://jk.gs/git-format-patch.html15:22
madewokherd left15:23
Seveas ech0s7: though do be aware that merge commits are not representable as patches, so if you have merges, this cannot be done.15:24
rchavik left15:24
osse GodGinrai: see my suggestion :p15:24
kaldoran left15:25
osse ToxicFrog: btw, git forbids ref names with a * in it. but I think the classic shell fork bomb is allowed15:25
ech0s7 Seveas: i haven't merges15:25
GodGinrai osse: I didn't see a suggestion in response to ech0s715:25
osse GodGinrai: oh, i misunderstood15:25
kaldoran joined15:25
sebboh joined15:25
osse that just sounds like git format-patch --all or somesuch15:26
EduardoMartins joined15:26
jimi_ left15:28
davisonio left15:28
ech0s7 thanks osse15:28
just looking a way to exclude the first commit :)15:28
fakenerd joined15:28
khmarbaise joined15:28
Derperperd left15:30
osse git format-patch firstcommit..HEAD15:30
ahmed_elgabri left15:30
synthroid joined15:31
synthroid left15:31
synthroid joined15:31
khmarbaise left15:32
ahmed_elgabri joined15:32
atomicb0mb joined15:32
rossome left15:32
rwswitch joined15:33
LionsMane left15:34
wilhelmtell joined15:34
LionsMane joined15:35
wilhelmtell left15:36
sebboh Hi! I'm trying to build some open source project, but that's not what my question is about. My question is, what knowledge am I missing about git which is preventing me from understanding what is happening? I'll describe what is happening... I've cloned a project called uzbl from github. I'm using git 2.8.1. Like some other projects, there's a master branch and a 'next' branch. So I tried `git checkout origin/next`. It says I am15:36
in a detached HEAD state. I don't recall seeing that message when I did the same thing on other projects. But I think too that I only did `git checkout next`, when switching to the 'beta' on other projects. Why did this one specify 'origin/next' in the install docs? Why am I in a detached head state? Does not each branch have its own HEAD?15:36
liamonade left15:36
eric97477 joined15:36
eric97477 left15:36
filcab left15:37
Gitzilla joined15:37
Seveas sebboh: 'origin/next' is not a branch, so if you check it out, your HEAD gets detached15:38
wilhelmtell joined15:38
jceb left15:38
Guest93616 left15:38
wilhelmtell left15:38
Seveas 'git checkout next' is a bit magical, it actually translates to 'git checkout -b next origin/next', so 'create branch next, tracking origin/next. And then check it out'15:38
sebboh I didn't download a list of branches when I cloned the repo?15:39
shams left15:39
davisonio joined15:39
Seveas you did, but those are stored as refs in refs/remotes, local branches don't get created automatically15:40
shams joined15:40
sebboh Does a simple git clone <Address> download everything that could possibly be downloaded? Is the result suitable for use as a historical archive of the repo at the point in time the clone was made?15:40
Seveas see https://git.seveas.net/recovering-from-a-detached-head.html and https://git.seveas.net/the-meaning-of-refs-and-refspecs.html for background info15:40
sebboh ok, thanks15:41
Seveas sebboh: it downloads everything downloadable, but that misses things like repo config and hooks, so it's not a complete backup15:41
Lipp left15:42
sebboh ok, understood.15:42
shinnya joined15:42
romerocesar joined15:42
liamonade joined15:43
leeN joined15:43
rossome joined15:43
byteflame joined15:43
Jibz left15:44
Balliad left15:44
mrkat joined15:46
abyx joined15:49
kbs oh, that looks a great site Seveas - nice; and one more handy link for me :)15:49
ShekharReddy joined15:50
wrouesnel1 left15:50
Muzer joined15:51
Dougie187 Seveas: Doesn't it also miss unreachable commits?15:51
hashpuppy joined15:52
ksolv joined15:52
Dougie187 Maybe those are considered not downloadable, but I think that distinction missing.15:53
Electrometro joined15:54
jstein left15:55
Lomex left15:55
Derperperd joined15:55
Lomex joined15:56
Lomex left15:56
madewokherd joined15:58
bambams I was hoping I could use GIT_DIFF_OPTS to get -w --ignore-blank-lines into git commit -v. It doesn't appear to work.15:59
Guest5 left15:59
bambams ack'ing the source it looks like it only looks for --unified and -u specifically...?15:59
morenoh149 joined15:59
Seveas Dougie187: it does. And the reflogs16:00
artemisart left16:00
Seveas https://git.seveas.net/how-to-back-up-a-git-repository.html :)16:00
cagomez left16:00
ahmed_elgabri left16:01
cagomez joined16:01
Guest5 joined16:01
Guest5 left16:01
mingrammer joined16:01
irco joined16:02
Guest5 joined16:02
dreiss joined16:04
Hounddog left16:04
ikmaak joined16:04
cagomez left16:05
ahmed_elgabri joined16:05
mingrammer left16:06
eivarv joined16:07
oich joined16:08
ksolv left16:10
zeroed left16:10
preyalone joined16:10
ahmed_elgabri left16:10
mrkat left16:11
govg left16:14
subhojit777 joined16:16
rossome left16:16
Guest5 left16:17
artemisart joined16:17
johntramp joined16:17
Guest5 joined16:18
spudowiar joined16:18
gitinfo set mode: +v16:18
astrofog left16:19
artemisart left16:19
mingrammer joined16:20
m0viefreak joined16:20
HappyLoa- left16:20
xall joined16:21
eivarv left16:21
ech0s7 left16:22
blackwind_123 joined16:22
Timvde left16:23
fahadash left16:23
liamonade left16:24
SteffanW2 joined16:24
mingrammer left16:24
garethdaine left16:24
HappyLoa- joined16:25
mSSM joined16:25
dsdeiz_ joined16:26
xall left16:27
dsdeiz left16:27
Timvde joined16:28
The_Phoenix left16:31
HappyLoa- left16:31
Noldorin joined16:31
nitric joined16:32
Electrometro left16:33
bambams http://explosm.net/comics/4388/16:34
kpease joined16:35
Vampire0_ joined16:35
dreiss left16:36
dreiss joined16:36
Vampire0 left16:37
nettoweb joined16:38
HappyLoa- joined16:38
cfxd left16:38
mahendra_ left16:39
Rodya_ left16:40
rossome joined16:41
kurkale6ka left16:42
albel727 joined16:42
EduardoMartins left16:43
Guest5 left16:43
jstein_ joined16:43
vaibhavsagar left16:44
jstein_jstein16:45
HappyLoa- left16:46
davisonio left16:48
rubyonrailed joined16:48
jheckman joined16:49
rubyonrailed left16:49
ahmed_elgabri joined16:50
xall joined16:52
daynaskully joined16:52
HoierM joined16:53
durham joined16:53
gitinfo set mode: +v16:53
jheckman I am running into a weird problem that I can't figure out. Earlier I cloned an internal repo, specifying the directory it should clone into. It cloned just fine but for some reason when I would fetch and reset nothing would actually change (but the log was correct). I deleted the folder and tried to clone again without specifying the folder and instead of cloning like normal, it is just showing the content of .git in the root of the chec16:53
If I try to checkout in a different place (like my home directory) it complains about the checkout in a different directory. This is on debian. I can't reproduce with the same repo on my mac16:54
ahmed_elgabri left16:54
lss8 left16:55
_ikke_ jheckman: A transcript of what you are doing would help a lot16:57
davisonio joined16:57
grawity hmm you aren't cloning with --bare or --mirror, are you?16:57
Impaloo left16:57
Impaloo joined16:57
HappyLoa- joined16:57
phaleth left16:57
jheckman not doing bare or mirror, one sec on transcript16:58
lss8 joined16:58
fakenerd left16:59
jost_ joined16:59
dreiss left16:59
jheckman jheckman@vm101:/var/git$ git clone git@internal_repo:ops/docker_config Cloning into 'docker_config'... remote: Counting objects: 41, done. remote: Compressing objects: 100% (32/32), done. remote: Total 41 (delta 9), reused 0 (delta 0) Receiving objects: 100% (41/41), 10.68 KiB | 0 bytes/s, done. Resolving deltas: 100% (9/9), done. Checking connectivity... done.17:00
that formatting is less than ideal though17:00
UTAN_dev left17:01
grawity hmm17:01
jheckman jheckman@vm101:/var/git/docker_config$ ls branches description hooks info logs packed-refs config HEAD index jenkins_master objects refs17:01
UTAN_dev joined17:01
jheckman jenkins_master is one of the folders within the repo, that for some reason that is where the code is17:01
grawity check that 'config' file, does it say "[core] bare = true"?17:02
jost left17:02
jheckman jheckman@vm101:~$ pwd /home/jheckman jheckman@vm101:~$ git clone git@internal_repo fatal: working tree '/var/git/docker_config/jenkins_master' already exists.17:02
grawity hmm17:02
_ikke_ type git17:03
jheckman bare is false in the config17:03
grawity env | grep GIT17:03
jheckman GIT_WORK_TREE=/var/git/docker_config/jenkins_master -- this was set for another script17:04
grawity kindly please unset it17:04
hdon joined17:05
_ikke_ grawity++17:05
jheckman reset my session, That fixed my problem. Thank you, should probably use a better variable name17:06
eivarv joined17:06
chll_ left17:06
Jonuz left17:06
_ikke_ GIT_WORK_TREE has a meaning to git17:06
phanimahesh joined17:06
Jonuz joined17:07
bongjovi left17:07
skylite left17:07
skylite joined17:08
jheckman good to know. I did not write the other script so maybe there was a reason it used that instead of something unique17:08
texinwien_ left17:08
roelmonnens joined17:09
dmto left17:09
Dougie187 Seveas: Oh sorry, I meant `git clone`. Not the proper backup method.17:10
Maybe I was plugging in to the wrong part of a conversation though. :P17:10
tgunr joined17:11
roelmonnens left17:11
roelmonnens joined17:12
_ikke_ jheckman: It's usually used in combination with git checkout on an existing repository to put the files in some directory17:13
jimi_ joined17:14
eivarv left17:15
jheckman left17:15
bambams (Sorry for the explosm link.. Wrong channel)17:16
eciohc joined17:16
weedtm joined17:16
jost_ left17:17
cyphase left17:17
InfoTest1 joined17:17
InfoTest left17:18
InfoTest1InfoTest17:18
nettoweb left17:18
fees left17:18
filcab joined17:18
weedtm left17:19
dan2k3k4 joined17:19
TooLmaN joined17:21
abyx left17:21
abyx_ joined17:21
boombatower left17:22
rossome left17:22
weckl left17:22
sanketdg left17:23
cyphase joined17:23
abyx_ left17:23
notebox left17:26
sanketdg joined17:28
notebox joined17:30
notebox left17:31
mostlybadfly joined17:32
fahadash joined17:32
roelmonnens left17:33
roelmonnens joined17:34
siaw23 joined17:34
rwswitch left17:35
siaw23 in my git log i have only 2 messages. the very first commit messages is wrong. i want to fix it. i tried ‘git rebase -i HEAD~2’ but it won’t show the 2 commit messages so i can pick which one i want to edit. it shows the last commit which is not what i want17:35
tgunr left17:35
siaw23 any idea how to fix old commit messages?17:36
grayjoc joined17:36
Ahmed90 joined17:36
aard_ joined17:36
siaw23 better if i can use the hash code to edit a particular commit message17:36
GodGinrai wouldn't HEAD~2 mean to go to a commit that doesn't exist?17:36
considering you only have 2 commits17:37
subhojit777 left17:37
bremner siaw23: pass the commit _before_ the one you want to edit to rebase -i17:37
oh. root commit. Yeah, there's a way, but I forget17:37
niranjan left17:37
GodGinrai siaw23: http://stackoverflow.com/questions/2119480/edit-the-root-commit-in-git17:38
siaw23 bremner: ok what if i have about 90 commits and i want to edit the 5th commit message?17:38
how would i do it?17:38
YourTheBombNow23 joined17:38
bremner then pass the commit before (so the 4th hash)17:38
romankl joined17:38
roelmonnens left17:38
YourTheBombNow23 left17:38
siaw23 so it would look like17:39
git commit hast_of_4th_commit —amend?17:39
_ikke_ siaw23: git rebase --root17:40
bremner no, git rebase -i hash_of_4th17:40
siaw23 bremner: ah ok let me try17:40
_ikke_: git rebase —root does nothing for me17:42
airdisa joined17:42
siaw23 i want to edit the root commit message17:42
infra-red joined17:42
dreiss joined17:43
_ikke_ siaw23: What do you mean, does nothing?17:44
infra-red left17:44
Spacew00t joined17:44
annoymouse_ joined17:44
_ikke_ AH, I thought it implied -i17:44
git rebase -i --root17:45
afuentes left17:46
LarArT joined17:47
iota_pi left17:49
dpower left17:50
iota_pi joined17:51
dsantiago left17:52
eciohc left17:52
mingrammer joined17:52
blackwell left17:53
siaw23 left17:53
blackwell joined17:53
todd_dsm_wk joined17:54
ASOLAr joined17:54
ASOLAr left17:55
Dyonisos joined17:55
moop left17:55
Guest5 joined17:56
grayjoc left17:56
BrianBlaze420 left17:56
mingrammer left17:56
siaw23 joined17:57
iota_pi left17:58
kinetik_ joined17:58
ash_workz left17:58
BrianBlaze420 joined17:58
siaw23 _ikke_: works now thanks :)17:59
gitinfo set mode: +v17:59
LarArT left17:59
nettoweb joined17:59
mSSM left18:00
govg joined18:00
MrMojito left18:00
iota_pi joined18:01
dpower joined18:01
moop joined18:01
Maple__Belgium18:01
MrMojito joined18:01
_ikke_ yw18:01
kinetik_ Hello guys. I am interesting on understand the inner workings of git revert. Can we say that git revert works the same way as the svn reverse merge ?18:02
fakenullie it just applies commit in reverse18:02
kadoban left18:03
_ikke_ Take a patch, change all + to - and - to +, apply18:03
kadoban joined18:03
kinetik_ I see.18:03
_ikke_ (where patch is the diff of the commit to revert18:04
BSaboia joined18:05
byteflame left18:06
Didac left18:06
b1tchcakes joined18:06
subhojit777 joined18:06
nanga left18:07
infra-red joined18:08
kinetik_ Let's say we have 3 sequential commits, and all change the first character of the file. Why reverting the second commit makes git throw a conflict cause it can't decide between the first and the third change? Why git doesn't assume that the last commit should be preferred when managing the conflict?18:08
fakenullie revert doesn't know anything about other commits18:08
romankl left18:10
_ikke_ kinetik_: Why is the last commit prefered?18:10
StuartMI joined18:11
_ikke_ kinetik_: When you revert a commit, you want the changes of that commit gone18:11
kadoban kinetik_: That specific revert seems like it would make no sense at all. Even thinking about it myself, I'd have no idea what you want the result to be. How could git know?18:11
roelmonnens joined18:12
cyan__ left18:12
BelgiumMaple__18:13
durham left18:14
ahmed_elgabri joined18:14
nanga joined18:15
eivarv joined18:15
kinetik_ _ikke_: because the last commit is closer to the right code, since it was the last change18:15
nidr0x left18:15
_ikke_ Not necessarily18:15
hseg joined18:16
davisonio left18:16
kinetik_ what I really want to do (regardless of which command), it's to take a out a specific commit from the repository. In a real-case scenario I want to take out a specific feature from the repository by removing the commit, as the feature doesn't belong to the code anymore avoiding manual intervention18:16
I thought revert was designed for that18:17
fakenullie git is stupid content tracker18:17
durham_ joined18:17
durham_ left18:17
davisonio joined18:18
durham_ joined18:18
_ikke_ Sure, but does not mean that reverting a commit would not commit with the current history18:18
fakenullie not feature management tool18:18
btree_ joined18:18
_ikke_ (last commit == conflict)18:19
kadoban kinetik_: You can certainly do that, with revert or otherwise. git doesn't know what your code means though, you have to resolve the conflicts that arise.18:19
AaronMT_ joined18:19
vaibhavsagar joined18:19
davisonio left18:20
mohabaks left18:20
btree left18:21
Didac joined18:21
AaronMT left18:22
kbs I also wonder if you mean revert in the sense of not having it in the history at all, as I wonder if git-revert actually does that?18:22
_ikke_ kbs: No18:23
kbs: That would be rewriting history18:23
kbs right18:23
_ikke_ kbs: git is basically creating a new 'undo' commit18:23
kbs but reading log above, I sorta wonder if that's the actual intent, and was curious18:23
because git-revert is easier to understand (in the not-actually-removing-history sense) as being a merge18:23
bocaneri left18:24
filcab left18:26
EvilPeng1 joined18:26
kinetik_ I appreciate that, but in my perspective if you take a commit in the middle of a pool of commits and conflicts arise shouldn't the commit after the left out one be the deciding base-source to manage any conflicts?18:26
spudowiar left18:27
kyan left18:27
kbs I think _ikke_ would know best, might strategy=recursive -Xours roughly approximate a merge that wanted to prefer HEAD on conflicts?18:27
kbs stays away from debates about about what should and should not be default behavior :)18:28
yan left18:28
dan2k3k4 left18:28
_ikke_ kinetik_: git plays safe and lets you decide18:29
kadoban kinetik_: Probably not. It requires human intervention to figure it out.18:29
roelmonnens left18:29
roelmonnens joined18:29
SonikBoom joined18:29
LionsMane left18:30
kinetik_ Ok. Thank you for your quick answers fakenullie, _ikke_ and kadoban18:30
subhojit777 left18:31
veilig2000 joined18:31
kinetik_ I guess it makes also sense because every commit is based on the previous one, so git plays safe not assuming more than it should18:32
fakenullie you can try branch from that commit, revert it in that branch and merge that branch18:32
but there will still be conflict, because commits in both branches changed that line18:33
roelmonnens left18:34
_ikke_ in any case, git revert does not look at the history at all18:34
Maple__ left18:34
cagomez joined18:35
hseg Hi. I'm trying to get a feel for my options w.r.t. subproject management. I have a couple of libraries that are used in multiple projects. How would I manage them?18:35
_ikke_ git can be summarized as: git diff <commit> <commit>~1 | git apply && git commit18:36
git revert*18:36
hseg It seems like I could use submodules, but I've heard a lot of bad stuff about it.18:36
fakenullie I've used git submodules successfully18:36
it's good when each project can break from library upgrade18:37
kbs ah, that's makes it very clear (re: git revert) thanks18:37
mohabaks joined18:37
Maple__ joined18:37
hseg fakenullie: What do you mean by "break from library upgrade"?18:37
fakenullie hseg: when library interface is unstable18:38
and needs to change18:38
or you just don't want to break other projects by changes in library18:38
Manuel15 left18:38
fakenullie we had dormant projects, so that worked good18:38
hseg Ah, OK.18:38
also, is it correct to summarize safe submodule usage as: "clients of a library only change the SHA they point to, all changes to the library are made in the library repo itself"?18:38
fakenullie it's only possible usage18:39
artemisart joined18:39
_ikke_ yes, that's correct18:39
hseg OK.18:39
_ikke_ Although nothing prevents you from comitting changes in the submodule repository18:39
It's your responsibility to share those changes18:40
romankl joined18:40
fakenullie you can refer them by write-only urls in project18:40
read-only18:40
dsantiago joined18:40
fakenullie that's how we did it, git:// url on github18:40
hseg How does a git:// github URL make it read-only?18:41
_ikke_ It doesn't18:41
hseg Then what did you mean by that remark?18:41
kinetik_ left18:41
ASOLAr joined18:42
fakenullie github does not allow write via git://18:42
or you can specify read-only user in url18:42
hseg Really?18:42
cagomez left18:42
sonOfRa left18:42
bremner almost nobody allows write via git://18:42
hseg Oh, for organizations I suppose.18:42
_ikke_ You can still commit in the repository18:42
hseg _ikke_: If you commit changes to the submodule, how do you keep them from being lost?18:42
_ikke_ and if you commit that commit in the parent repo, no one is able to find hte commit18:43
fakenullie hseg: you push them18:43
Manuel15 joined18:43
Manuel15 left18:43
Manuel15 joined18:43
ASOLAr left18:43
grayjoc joined18:43
hseg OK. Then what's this about commits being lost?18:44
fakenullie I'm not sure18:44
_ikke_ You need to make sure they're pushed18:44
hseg Otherwise, what happens? Suppose I committed a local patch to a library I use, then pull from upstream?18:45
diegoviola joined18:45
sonOfRa joined18:45
fakenullie the change will be merged or rebased into upstream18:45
_ikke_ It gets merged18:45
fakenullie maybe "lost" change are then someone forgets to commit and push submodule changes18:46
_ikke_ yes18:46
cdg left18:46
hseg assuming I'm tracking a remote branch. So submodules are no different from regular repos?18:46
_ikke_ or commit them, commit them in the parent repo, but never push18:46
fakenullie yeah18:46
_ikke_ Then other ones try to check out the submodule but cannot find the recorded commit18:46
davisonio joined18:47
hseg OK, so don't update the library version used in the project without pushing the library commits first.18:47
_ikke_ correct18:48
hseg And seeing as submodules are considered binary blobs w.r.t. git, resolve merge conflicts in the submodules before fetching from upstream in the project.18:49
Doesn't seem like they deserve the bad press they seem to be getting.18:49
(he said, unaware of the hours of sadness ahead of him)18:50
ash_workz joined18:50
fakenullie well, unpushed submodules happen quite often18:50
hseg Oh? Why?18:51
satifant joined18:51
veilig2000 left18:51
fakenullie people forget18:51
axelitus joined18:51
fakenullie iirc you have to go into submodule and push explicitly18:52
nikivi left18:52
hseg Eh. OK.18:52
fakenullie so if someone does that on goes on vacation it can be tough18:52
hseg Right. As usual, make sure to leave history in consistent state before getting hit by a bus.18:53
_ikke_ It's better to not directly work in the submodule dir18:53
hseg OK, will avoid doing that.18:53
_ikke_ thinks read-only submodules should be a thing18:53
veilig2000 joined18:54
hseg Yeah... If you actually need to patch the submodule, wouldn't it be saner to clone the submodule repo as a repo in its own right, develop on it, and use the clone as a submodule?18:55
fakenullie it's more convenient to make changes together18:55
_ikke_ yes, but also more error prone18:56
hseg Why?18:56
_ikke_ For the reasons we just mentioned18:56
zacts joined18:56
hseg I develop libfoo-v1-internal, then set project bar to use that version of libfoo instead of the upstream version.18:57
NightStrike I just did a "git checkout -b XX".... how do I rename that to YY ?18:57
davisonio left18:58
nettoweb left18:58
hseg Keeping track of work within libfoo works just as usual, and the only thing to keep in mind is to only change library version used once the corresponding commit is pushed18:58
NightStrike: git branch -m XX YY18:59
FuzzySockets joined18:59
NightStrike hseg: thanks18:59
davisonio joined18:59
nettoweb joined18:59
Maple__ left18:59
MrMojito left19:00
jnewt joined19:00
MrMojito joined19:00
MrMojito left19:00
MrMojito joined19:00
Maple__ joined19:00
jnewt i'd like to set the author & commit date of one commit to the same as another (i split a commit buried in history, but didn't preserve the acutal dates of the file changes (which i would like to))19:00
i have the sha of the old commit and the sha of the new commits.19:01
_ikke_ jnewt: look into git commit -c / -C19:02
siaw23 i did a rebase and i have my profile pic appearing on commits fromt he point i did the rebase. how do i revert this? https://gyazo.com/6294feabb16524e043b36d3a16fc31cd19:02
dan2k3k4 joined19:02
_ikke_ (you do have to restore the message though)19:02
xdinomons joined19:03
xall left19:03
_ikke_ siaw23: This is probably because comitted date is different from author date19:03
NeonSynth joined19:04
siaw23 but this has affected my app and tests are failing now19:04
but there’s no code change :(19:04
_ikke_ Why?19:04
jnewt _ikke_, is there a way to get the commit date of a commit by sha?19:04
_ikke_ Why should your app fail on this?19:04
siaw23 i don’t know why the test are failing after. since there’s not code change19:04
l4v2 left19:04
_ikke_ jnewt: look at man git show --format19:04
gitinfo jnewt: the git-show manpage is available at http://jk.gs/git-show.html19:05
preyalone left19:05
l4v2 joined19:05
siaw23 i just edited an older commit using rebase and reword19:05
Pinkamena_D left19:05
eivarv left19:05
xdinomons how do i make a bare repository available to anyone like a webserver19:05
snowkidind left19:05
_ikke_ xdinomons: dumb http is easiest, but requires you to execute git update-server-information regularly19:06
siaw23: Why would that break your app?19:07
MrMojito left19:07
siaw23 _ikke_: i don’t know why it’s doing that honestly19:07
_ikke_ siaw23: find out why the tests are failiing19:07
failing19:07
MrMojito joined19:07
monk12 joined19:08
eivarv joined19:08
xdinomons ohh just read an article that ssh is best19:09
infra-red left19:09
monk12 Hey all, Im using git with Eclipse. I was curious... i forked a project in BitBucket (so its my personal playground for a project)... in Eclipse i had the original origin Remote. but also just added a new Remote for my personal fork... how does Eclipse know which Remote to send it to by default (pretend its the same branch in both remotes)?19:09
_ikke_ xdinomons: yeah, imo it's the best19:10
siaw23 _ikke_: is there a way to revert the rebase i made?19:10
_ikke_ monk12: git has so called tracking information19:10
monk12 how does it know which Remote to send to currently. Im wondering how I can find that out or change it via GUI/Eclipse and command line git.19:10
siaw23 i honestly don’t know why my tests are failing19:10
xdinomons left19:10
monk12 so if the checked out branch in Eclipse was originally associated with the origin remote... how can i change to new remote be4 my Push?19:11
Derperperd left19:11
_ikke_ siaw23: A beter thing would be to diff the changes from before and after19:11
monk12: I don't know how to do it in eclipse19:11
siaw23 _ikke_: i thought of that but i’m not sure what to diff against what19:11
_ikke_ siaw23: look at man git reflog19:11
gitinfo siaw23: the git-reflog manpage is available at http://jk.gs/git-reflog.html19:11
_ikke_ This keeps track of HEAD and your branches so that you can retrieve back commits19:12
monk12 _ikke_: its might be Right CLick->Properties in the configuration... u can change... _ikke_: how about on the command line? how can you check and change a remote for a branch.19:12
just curious how to do it the proper way on command line19:12
_ikke_ monk12: easiest is git push -u <remote> <branch>19:13
the -u will make git update the tracking info19:13
mohabaks left19:13
monk12 _ikke_: cool... i think i also got a way to report it tooo..19:14
_ikke_: git branch -vv (two v's)19:14
seems to work19:14
_ikke_ monk12: correct19:15
merpnderp joined19:15
monk12 sweet... thanks _ikke_ ... this really helps19:15
_ikke_ git status will also mention it for the current branch19:15
git checkout19:15
mingrammer joined19:16
merpnderp We have a react project in git. But we don't want to regularly check in our builds. But we do want to deploy those builds with git. Are there sub projects that we'd only commit and push to a sub repo for that build folder?19:16
GodGinrai merpnderp: git is not a deploy tool19:18
romankl left19:18
GodGinrai merpnderp: you shouldn't use it as one19:18
siaw23 _ikke_: i think the head somehow moved to another point19:19
Pinkamena_D joined19:19
filcab joined19:20
mr_quincy joined19:20
davisonio left19:20
mingrammer left19:21
jeffmjack joined19:21
artemisart left19:21
grayjoc left19:23
merpnderp GodGinrai: git is actually a great deploy tool if you want to use it as one.19:24
Lots of people happily use it that way day in and day out.19:24
Github et al have special git deployment keys just for using a special key for deployments.19:25
hseg left19:25
MainB left19:25
boyen left19:25
palmira67 joined19:25
GodGinrai merpnderp: A lot of people use excel to keep track of their work, but JIRA et al do a much better job19:25
SteffanW2 left19:26
GodGinrai merpnderp: github deploy keys are for deployment tools to use to clone the repo *during* the deploy process.19:26
git itself isn't the deployment tool19:26
Derperperd joined19:27
gitinfo set mode: +v19:27
mr_quincy I inherited a "non-bare" git repo, and I'm getting a strange result from running "git status" from the master branch. It says "On branch master" and on the next line says "Your branch is ahead of origin/master by 7 commits". This should not be. The master branch should be identical to the origin/master branch.19:27
jimi_ left19:27
davisonio joined19:28
tobiasvl mr_quincy: well apparently it's not, but your origin/master might not be up to date with origin's master19:28
do a git fetch19:28
GodGinrai mr_quincy: They might not be identical in commits19:28
merpnderp GodGinrai: so the deployment tool does git clone or git pull. Like my fingers will do on the CLI.19:28
GodGinrai what tobiasvl said, too19:28
siaw23 _ikke_: ok the problem is this “Your branch is ahead of 'origin/rails4_clone' by 125 commits.19:29
(use "git push" to publish your local commits)19:29
nothing to commit, working directory clean”19:29
_ikke_: how can i fix that please. i don’t want to risk to get things worse19:29
Pinkamena_D left19:29
siaw23 is it because i used rebase?19:29
GodGinrai merpnderp: the deployment tool will clone so that it can get the source for building/deploying19:29
siaw23 because i don’t see how my branch can be ahead 125 commits19:29
that’s why my tests are failing :(19:30
GodGinrai merpnderp: if you don't intend to "control" your source, there is no reason to be using git19:30
paul424 joined19:30
merpnderp GodGinrai: What do you mean? I want a submodule for our build folder. We run a build that we decide is ready for deployment. Check it in to the submodule's master. And then on prod we can do a git pull.19:31
What's wrong with that?19:31
GodGinrai siaw23: did you try the fetch command like tobiasvl suggested?19:31
tobiasvl that was for mr_quincy19:31
but applies for siaw23 too probably19:31
siaw23 GodGinrai: i didn’t see his “fetch” suggesting19:31
kpease left19:32
LionsMane joined19:32
siaw23 git fetch is not the same as git pull?19:32
GodGinrai !deploy19:32
gitinfo Git is not a deployment tool, but you can build one around it (in simple environments) or use it as an object store(for complex ones). Here are some options/ideas to get you started: http://gitolite.com/deploy.html19:32
arand joined19:33
GodGinrai siaw23: `git pull` === `git fetch; git merge origin/master` essentially19:33
when run from master19:33
johnmilton left19:34
mniip joined19:35
_Cyclone_ joined19:35
kpease joined19:35
ki0 left19:35
fractalizator joined19:35
paul424 left19:36
siaw23 how do i set the head to the current commit?19:37
i think that’s what’s bugging me19:37
Bizkit joined19:37
GodGinrai siaw23: HEAD is where the current commit is19:37
that's what HEAD means19:37
siaw23 i thought you could set it to which commit you would like19:38
dodobrain joined19:38
GodGinrai siaw23: when you do, that changes which commit is the "current commit" for a branch19:38
ExoUNXJohn19:38
siaw23 yes19:38
JohnJohn_Doe19:38
John_DoeExoUNX19:39
siaw23 my tests is failing i think for this reasong “Your branch is ahead of 'origin/rails4_clone' by 125 commits.”19:39
but i don’t understand why my local repo can be AHEAD19:39
and i want it to be the same as the remote repo19:39
Spacew00t left19:39
fakenullie you pulled commits from other branch19:39
yitz ls19:40
fakenullie . ..19:40
yitz If someone checked a massive binary into a repo and I did a 'git rm', how do I clear it out of the .git to shrink my repo size?19:41
fakenullie you can't19:41
it's forever there unless you change the history19:41
perlpilot yitz: rewrite the commits such that it's not there anymore19:41
yitz >.>19:41
khmarbaise joined19:41
nettoweb left19:41
yitz How do I do that?19:43
shaggycat joined19:43
fakenullie https://help.github.com/articles/remove-sensitive-data/19:44
siaw23 left19:45
l4v2 left19:46
kapu left19:46
circ-user-RNfpp left19:46
l4v2 joined19:47
yitz If I got to a detached HEAD, how do I get back to the ... origin HEAD?19:47
Oh. origin/HEAD :)19:47
arooni i added a file to not be ignored via a .gitignore file; yet when it try to add the file it tells me its still part of the git ignore file.. why?19:47
kapu joined19:47
arooni do i need to commit the changes to the ignore file firsT?19:48
eka left19:48
fakenullie arooni: something is wrong, you don't need to commit it19:48
yoan joined19:48
arooni why does git hate me19:49
Bizkit left19:49
circ-user-RNfpp joined19:49
fakenullie I guess you made a mistake19:49
arooni in my ignore file i have * ; then later i have !bin/pbcopy-remote .. located in ~/bin/pbcopy-remote19:49
gitinfo [!binary] Storing binary files in git causes repo balloon, because they do not compress/diff well. In other words, each time you change a file the repo will grow by the size of the file. See !annex for some solutions19:49
paul424 joined19:50
mr_quincy tobiasvl: Thanks for the tip. I want my master to become origin/master. Ordinarily I would git add, git commit, and git push origin master. When I try to push however, I get an error message related to non-bare repositories. I don't want to create an inconsistent work tree, but I do want to push my local master branch to the origin/master branch.19:51
Sasazuka__ joined19:51
fakenullie mr_quincy: your remote is non-bare repository19:51
vaibhavsagar left19:52
zeroed joined19:53
zeroed left19:53
zeroed joined19:53
mr_quincy fakenullie: that seems consistent with the messages I'm seeing. Why would anyone use a non-bare repo? I haven't seen one before I inherited this.19:53
Sasazuka__ left19:53
fakenullie mr_quincy: did you clone from non-bare repository?19:54
tobiasvl mr_quincy: perhaps the remote has only been pulled from, not pushed to in the past?19:54
Sasazuka__ joined19:54
hjubal left19:55
mr_quincy fakenullie: unfortunately I'm not certain how this clone was initially created. It does seem likely that no one has ever pushed to this. It was kind of an abandoned undergraduate project19:55
tobiasvl do you need to push to it?19:55
Sasazuka__Sasazuka19:56
tobiasvl do you have access to the remote somehow?19:56
veilig2000 left19:56
yitz ...how do I attach my HEAD? I did a checkout origin/HEAD19:57
mr_quincy Ideally, I'd like to push the changes that haven't been committed yet, just so I have a complete history. Once that's done I'll wipe this .git out and create a bare repo for my future developments.19:57
I do have access to the remote19:57
admin rights as well19:57
on the fs where the remote is located19:57
grawity yitz: checkout an actual branch19:57
shaggycat left19:58
fakenullie mr_quincy: you can clone it into bare repo and then push to it19:59
or you can push to new .git19:59
yitz grawity: Thanks19:59
InfoTest left20:01
cdg joined20:02
nettoweb joined20:02
thiago joined20:03
foist joined20:05
Sasazuka left20:05
Guest5 left20:05
t-mart left20:05
mr_quincy fakenullie: Please feel free to tell me if I'm doing something stupid, but it seems cleaner to push these changes to the non-bare origin as a kind of "final backup" before I create a bare repo. This repo contains a subset of the source I wish to control moving forward.20:05
fakenullie mr_quincy: create new bare repo and push to it, without changing old repo20:06
t-mart joined20:06
shams left20:07
Guest5 joined20:07
HoierM left20:07
zacts left20:08
xall joined20:08
hjubal joined20:08
SirCmpwn left20:08
vaibhavsagar joined20:09
JacobsLadd3r joined20:09
jeffreylevesque left20:09
JacobsLadd3r left20:10
mr_quincy fakenullie: thanks, I'll do that. What's the use case for a non-bare repo?20:11
zumba_addict joined20:11
le_melomane joined20:11
fakenullie mr_quincy: work with it?20:11
zumba_addict folks, when my ofcmate was doing git revert on a sha 3 commits ago, it's failing20:11
i only told to do a git log and find the sha20:12
Narwhaal left20:12
fakenullie failing?20:12
zumba_addict then also told him to do a git revert the_sha_key_here20:12
yeah20:12
it's failing20:12
rossome joined20:12
fakenullie what error20:12
zumba_addict one sec, let me ask him to forward the error to me20:13
CheckDavid left20:13
sanketdg left20:13
zumba_addict he's sending it20:13
grayjoc joined20:13
Narwhaal joined20:14
nwkj86 joined20:16
mostlybadfly left20:17
javier_ joined20:18
Sasazuka joined20:18
dodobrain left20:19
zumba_addict gheez, i LOL hard, he git revert someone's code20:19
can we undo the revert?20:20
fakenullie you can revert a revert20:20
zumba_addict so the sha of the last revert right?20:20
GodGinrai and revert a revert of a revert20:20
fakenullie yes20:20
zumba_addict hahaha :D20:20
he is friggin scared man! LOL20:20
and teammates where wondering why i was laughing so hard20:20
brb20:20
Derperperd left20:21
merpnderp Thanks GodGinrai that was good stuff.20:21
mr_quincy fakenullie: I misspoke, sorry. Reading a bit to ask a better question. Is there a use case for establishing non-bare remote origin? I hope I asked that correctly...20:21
GodGinrai merpnderp: np20:22
btree_ left20:22
fakenullie mr_quincy: well, he may worked on it, and then he cloned it in a new place20:22
sbeex joined20:22
fakenullie mr_quincy: he did not plan to push20:22
grayjoc left20:22
sbeex good evening20:23
fakenullie clone just kept source repository as origin20:23
mr_quincy: or he pushed to non-checked out branches20:23
SirCmpwn joined20:23
ajf- joined20:24
mablae joined20:26
rwb left20:26
ajf- left20:27
netcarver joined20:27
zumba_addict fakenullie: finally received the error message - error: Commit ef058f25291fecf952abf027d3f797ec4 is a merge but no -m option was given.20:27
mr_quincy got it. Thanks fakenullie, you've been very helpful.20:27
_ikke_ zumba_addict: says it all20:27
zumba_addict then next line fakenullie fatal: revert failed20:27
what do we have to do?20:28
_ikke_ zumba_addict: Do you actually want to revert a merge?20:28
zumba_addict he just wants to revert all the things he updated20:28
jimi_ joined20:28
cyan__ joined20:28
zumba_addict git log shows it20:28
_ikke_ git revert would not remove it from git log20:28
thiago left20:29
zumba_addict yup, I'm aware20:29
fakenullie git reverting a merge is not trivial20:29
zumba_addict he just want to remove the errors he introduced20:29
Sasazuka left20:29
Sasazuka joined20:29
zumba_addict so he wants to git revert the sha that git log is showing but we're getting that error above20:29
artemisart joined20:29
fakenullie you have to specify which branch you want to get rid of20:29
zumba_addict we are in master20:30
kaldoran left20:30
eivarv left20:30
zumba_addict so if it's a merge, we have to specify that branch that we merged into master?20:30
fakenullie fakenullie: look at a commit, see which branch is master20:30
which parent of it is master20:30
zumba_addict which command would show it?20:31
will git log show it?20:31
fakenullie yes, search for -m in git revert20:31
man git revert20:31
gitinfo the git-revert manpage is available at http://jk.gs/git-revert.html20:31
zumba_addict ok20:31
-m parent-number so parent-number is the sha?20:31
fakenullie I can't remember which command shows parents20:31
_ikke_ zumba_addict: parent number is always 120:31
zumba_addict so -m 1 ?20:32
_ikke_ yes20:32
zumba_addict so git revert -m 1 theshaofthecommit20:32
_ikke_ It tells git revert which side of the revert to 'keep'20:32
nettoweb left20:33
jadew joined20:35
jadew hey, is it still not possible to add an empty folder to the index?20:35
Ineentho[m] left20:35
milki jadew: it will never be allowed20:35
jadew milki, why never?20:35
aard_ left20:35
milki folders arent tracked by git at all20:35
jadew well, yeah, but why would it never be allowed20:36
milki jadew: this is a very low-level git specification20:36
jadew it seems like a big oversight20:36
I see, so no plans to fix it20:36
milki jadew: a question we would ask is why do you need a folder?20:36
NeverDie joined20:36
ResidentBiscuit It's nothing to "fix"20:36
It's not a bug20:36
jadew milki, because an empty folder or folder structure for that matter can be part of a project20:36
it's not always the contents of the files that matter20:36
milki jadew: we believe its not the responsbility of git to track non-code things like folders20:36
Pinkamena_D joined20:37
TooLmaN left20:37
milki jadew: why does the project require empty folders?20:37
tjbp joined20:37
jadew milki, for structure20:37
milki what does that mean?20:37
jadew it means that some stuff may go in there in the future and there's a place for that20:37
it may also be as part of a template20:38
perlpilot jadew: a common mechanism is to put a .gitignore file in the directory and add that to the repo20:38
jadew perlpilot, yeah, that doesn't seem like a decent solution20:38
perlpilot jadew: another is to have your deployment mechanism build the needed directory structure20:38
milki jadew: this sounds like a workflow responsibility rather than a code repository responsibility20:39
lamont left20:39
jadew milki, the code may rely on those folders being there20:39
crayon joined20:39
jadew anyway, I see your point20:39
milki your application should be able to handle the creation of folders during runtime or configuration20:39
crayon left20:39
crayon joined20:39
milki jadew: and its best not to run your applications straight out of the repo20:39
Ineentho[m] joined20:40
zumba_addict sorry was in his cube20:40
jnewt just put a blank .gitignore in the folder20:40
zumba_addict so I saw the branch that was merged into master20:40
jadew jnewt, yeah, silly solution20:40
how is that part of the code?20:40
the point is that various projects need this sort of functionality and forcing the user to do shitty stuff like putting .gitignoore files or dummy files in there doesn't seem to make sense20:41
zumba_addict ah _ikke_ since it's a merge say branch_A into master with a sha of abc123, the command will be git revert -m 1 abc123?20:41
jnewt it's not, but it will solve the problem of not having folders you create stick around.20:41
jadew jnewt, I know, I've been using dummy files in the past, right now I was just countering the point that "it shouldn't do it"20:42
GodGinrai left20:42
perlpilot jadew: It is a little weird that git doesn't treat directories as files (just like unix does). But, it is what it is.20:43
ResidentBiscuit git tracks files, not directories. If that doesn't suit your needs, don't use git20:43
jadew ResidentBiscuit, how's that an argument?20:43
dmto joined20:43
ResidentBiscuit It's not an argument, it's a fact of life. If a tool doesn't do what you need, don't use the tool20:43
jadew perlpilot, I agree20:43
zumba_addict i found this in stackoverflow,i it20:44
jnewt are we arguing about something?20:44
jnewt is late to the party20:44
zumba_addict it's git log output, Am i right that first value is parent? Merge: 8989ee0 7c6b23620:44
morenoh149 how do I list the current changes when committing?20:44
javier_ left20:44
zumba_addict i mean 8989ee0 is the parent 1 which is master?20:44
jnewt morenoh149, git status20:44
morenoh149 I think it's a thing added by zsh and I miss it20:44
kbs jadew: basically, you're right that git doesn't support empty folders; and for fairly basic choices made in its design. It's reasonable to want it to do it if it can, and the main reason it doesn't exist is fundamentally a symptom, not an explicit goal per-se.20:44
morenoh149 jnewt: I used to be able to do `git commit` and I'll be prompted with vim and a diff below my commit message20:45
MrMojito left20:45
jnewt git diff .20:45
morenoh149 this way I can write the commit message while reviewing the changes to be commited in a single vim window20:45
jadew kbs, makes sense, thanks20:45
I thought it's a design decision20:46
zumba_addict he couldn't wait, he edited the file again, lol20:46
lamont joined20:46
thiago joined20:46
atomicb0mb left20:46
hjubal left20:46
morenoh149 jadew: git commit -v20:46
https://gist.github.com/bkono/635850620:47
now I need colors 8)20:47
CheckDavid joined20:47
fmcgeough left20:48
cagomez joined20:50
mariuscc left20:50
morenoh149 dash vee son20:51
kutsuya left20:53
morenoh149 ah that's a vim setting actually20:53
synthroid left20:54
nettoweb joined20:54
leeN left20:58
EvilPenguin joined20:59
ExoUNX left21:00
EvilPeng1 left21:00
thibaultcha joined21:01
Pinkamena_D left21:01
Guest5 left21:02
circ-user-RNfpp left21:02
mingrammer joined21:05
dan2k3k4 left21:07
Cihan joined21:08
ShekharReddy left21:09
cagomez left21:09
cyan__ left21:09
mingrammer left21:10
mniip left21:10
mda left21:11
Dyonisos left21:11
SporkWitch left21:11
SporkWitch joined21:11
glebihan_ left21:12
adron joined21:12
kyan joined21:13
paws_ joined21:14
cyan__ joined21:14
glebihan_ joined21:14
osse pro tip, if you ever forget -v you can do :$r!git diff --staged21:15
mingrammer joined21:15
osse nnoremap SHIT :$r!git diff --staged<CR>``21:15
hmm21:17
might be easier to :q and git commit -v21:17
dodobrain joined21:17
satifant left21:18
mingrammer left21:19
ericP joined21:20
ericP left21:20
mda1 joined21:20
mattcen left21:22
ash_workz left21:24
mattcen joined21:28
t0by left21:28
sagerdearia left21:29
Literphor joined21:31
blackwind_123 left21:31
aard_ joined21:33
blackwind_123 joined21:33
cd-rum joined21:33
khmarbaise left21:33
Manuel15 left21:35
LucaTM left21:35
veilig2000 joined21:36
f0rblaze left21:36
adron left21:37
cd-rum_ joined21:37
sagerdearia joined21:37
veilig2000 left21:37
Manuel15 joined21:37
Manuel15 left21:37
Manuel15 joined21:37
fractalizator left21:37
zeroed left21:38
cd-rum left21:38
mycyber joined21:39
ResidentBiscuit left21:39
texinwien_ joined21:39
mellernoia joined21:39
cyphase left21:40
cyan__ left21:41
veilig2000 joined21:41
JamesBaxter left21:43
cyphase joined21:44
Gitzilla left21:46
robotroll joined21:46
mycyber left21:46
jeffmjack left21:48
le_melomane left21:49
axelitus left21:49
robotroll left21:51
thiago left21:51
Dougie187 left21:51
unbalanced joined21:52
unbalanced left21:56
veilig2000 left21:57
madewokherd left21:58
texinwien_ left22:00
AaronMT_ left22:00
TomyLobo left22:01
veilig2000 joined22:01
cortexman joined22:02
aard_ left22:02
davisonio left22:02
monk12 left22:02
cortexman is there a way to have a meta-repository that has the behavior when you "git clone" it clones all the repositories that it points to, and that when you "git pull" it updates to the latest version of all the repositories that it points to?22:03
DeJoker joined22:03
irco left22:05
rgrinberg left22:06
jhass you might want the repo tool from the android project https://code.google.com/p/git-repo/22:06
cortexman it wasn't clear to me how general that tool is22:08
sbeex left22:09
osse Poor man's alternative: use git clone --recursive, and put 'git submodule update' in .git/hooks/post-merge and .git/hooks/post-checkout22:10
cortexman osse, those hooks go in all submodules?22:10
zivester left22:11
osse no22:11
they go in the outer repo22:11
spudowiar joined22:11
adron joined22:11
gitinfo set mode: +v22:11
cortexman osse, how will i then update?22:12
git pull?22:12
osse yes22:12
StuartMI left22:12
cortexman nice22:12
DeJoker left22:12
mycyber joined22:12
netcarver left22:13
StuartMI joined22:13
osse but this requires some manual steps to set up. maybe the android repo tool is better in this regard22:13
b1tchcakes left22:13
cortexman if i could set up the meta repository such that users just type repo init, etc, that would be ideal22:13
Ineentho[m] left22:14
Ravana left22:14
vassagus_ joined22:14
adron left22:14
osse that's not happening with vanilla git22:14
adron joined22:14
pioiytr left22:14
osse but you could put a script in the outer repo that will set things up after they clone it22:15
vassagus left22:15
cd-rum_ left22:15
darkbit left22:16
cagomez joined22:17
Ravana joined22:17
zumba_addict left22:18
evanvarvell left22:19
Ineentho[m] joined22:20
jaafar left22:20
jaafar joined22:21
perlpilot left22:22
perlpilot joined22:23
macivy left22:23
cdg_ joined22:24
veilig2000 left22:24
cdg left22:25
Shakeel__ left22:25
nettoweb left22:25
ahr3n joined22:26
cd-rum joined22:26
Shakeel_ joined22:26
nettoweb joined22:29
boombatower joined22:29
thiago_ joined22:29
cd-rum left22:31
dhollinger left22:31
madewokherd joined22:34
artemisart left22:34
artemisart1 joined22:35
l4v2 left22:36
cjohnson joined22:37
cjohnson When I make a new branch and git push origin newbranch22:37
I always have to come back and --set-upstream-to22:37
How can I tell git to be smarter about that?22:37
osse cjohnson: use -u the first time you push22:38
mingrammer joined22:38
osse -u = --set-upstream22:38
cjohnson sweet. is there also a shorthand to say "use the same branch name on remote"?22:38
osse yes. you're already using it22:38
git push origin newbranch is the same as git push origin newbranch:newbranch22:39
for something even shorter and/or general I think git push origin HEAD will work22:39
cjohnson Oh I guess I mean, even shorterhand to say "use the current branch"22:39
gotchya22:39
paul424 left22:39
cd-rum joined22:40
osse git config alias.topkek 'push -u origin HEAD'22:40
then git topkek22:40
\o/22:40
red_ joined22:41
kpease left22:41
b1tchcakes joined22:42
cd-rum_ joined22:43
Spec-Chum joined22:43
mingrammer left22:43
NightStrike I have a commit that has changes from 2 files... it's supposed to be 2 commits one for each file... how do I split that?22:43
thiago_ left22:43
cd-rum left22:44
mingrammer joined22:45
garethdaine joined22:45
l4v2 joined22:45
nedbat NightStrike: is it the latest commit on your current branch?22:46
NightStrike yeah22:47
osse git reset HEAD~; git add file; git commit; git add file2; git commit22:47
NightStrike osse: thanks!22:48
dsdeiz_ left22:49
mingrammer left22:49
crayon left22:50
ahmed_elgabri left22:50
Orion3k left22:51
le_melomane joined22:53
mr_quincy left22:53
Orion3k joined22:54
rkazak joined22:55
Derperperd joined22:56
FuzzySockets left22:56
red_ left22:56
adron left22:57
adron joined22:57
crayon joined22:58
thibaultcha left22:58
cortexman left22:58
bartosz_ left22:59
jimi_ left22:59
crayon left22:59
alansaul left23:00
crayon joined23:01
Rodya_ joined23:01
crayon left23:01
SonikBoom left23:01
CheckDavid left23:03
l4v2 left23:03
Tobarja left23:03
ams__ left23:04
ahr3n left23:04
crayon joined23:04
cagomez left23:05
Finnoloid left23:07
artemisart1 left23:07
xaa left23:08
crayon left23:09
crayon joined23:09
LionsMane left23:09
nwkj86 left23:09
rwb joined23:10
mycyber left23:10
red_ joined23:13
liamonade joined23:13
yitz After a `git fetch origin master` how do I see the diff between local HEAD and origin/master/HEAD ?23:13
zivester joined23:13
osse git diff HEAD origin/master23:14
GenZai left23:15
osse origin/master/HEAD isn't a thing23:15
yitz That command is showing no output >.>23:16
osse Then there are no differences23:17
ljc joined23:17
yitz But `git fetch origin master` showed: remote: Total 31 (delta 20), reused 16 (delta 9)23:17
osse It probably fetched more than just master23:18
timewalker joined23:18
ljc left23:19
dodobrain left23:20
dodobrain joined23:20
Rodya_ left23:20
al-damiri left23:20
kn-928 joined23:21
saedelaere left23:26
rahtgaz left23:29
dsdeiz joined23:29
dsdeiz left23:29
dsdeiz joined23:29
alansaul joined23:30
alansaul left23:31
alansaul joined23:31
adron left23:33
JanC_ joined23:35
JanC left23:36
vassagus_ left23:36
JanC_JanC23:36
Derperperd left23:38
vassagus joined23:38
mablae_ joined23:39
Derperperd joined23:39
nilg joined23:40
dmto left23:40
_sjs joined23:42
AbstractArtist joined23:42
mablae left23:43
garethdaine left23:43
afuentes joined23:44
ahr3n joined23:46
cdg_ left23:47
cdg joined23:47
a3Dman left23:50
RustyShackleford joined23:52
cdg left23:53
kulyzu joined23:53
kulyzu left23:53
a3Dman joined23:53
kulyzu joined23:53
Spec-Chum left23:54
foist left23:54
nilg left23:54
Spec-Chum joined23:54
Thorn__ left23:54
mellernoia left23:56
pcre_ left23:57
Ahmed90 left23:58
kulyzu left23:59

Logs Search ←Prev date Next date→ Channels Documentation