<prefixcactus>
also: is there a better way of squashing the whole thing into one patch besides making a throwaway branch just for that?
<apritzel>
prefixcactus: git rebase -i
<apritzel>
or do you mean while still keeping the history of patches in a separate branch?
<prefixcactus>
wouldn't that also destroy the commits, which I want to keep?
<apritzel>
I typically have a devel branch, where I just pile the fixes up as I go
<apritzel>
then branch off a clean branch, where I prepare the patches in the right order, for submission
<karlp>
I do that too..
<karlp>
you can have lots of branches, use them for various views of things :)
<prefixcactus>
so you just fork a branch off of the common ancestor, merge the devel branch there without committing, and construct the series of patches from those changes?
<karlp>
no, I have branch "mydev" with 20 commits all splshed together
<apritzel>
prefixcactus: you branch off the top of your devel branch, then use git rebase -i to create the actual patches
<karlp>
then just branch again frrom there
<karlp>
and rebase off "where you want to merge back to"
<apritzel>
yes
<prefixcactus>
apritzel: ahhh, I see. That does indeed sound better than what I described
<karlp>
(you definitely don't want to to trye diting the patches in git send email asyou go...)
<apritzel>
branches are super cheap in git, the only limit is layer 8 getting overwhelmed with the sheer number at some point
<apritzel>
I have an alias to list them in chronological order, that helps: alias gbt='for _i in $(git branch | cut -c3-); do git log -1 --pretty="%ci $_i" $_i; done | sort -n'
<prefixcactus>
what does gbt stand for?
<apritzel>
that's the alias name, something like "git branch time"
<karlp>
I use naming conventions, but yeah, it can get messy :)
matthias_bgg has quit [Ping timeout: 264 seconds]
<apritzel>
prefixcactus: and if you do revisions (v2, v3, ...), you can pile the fixes on top of that branch that you sent out, then repeat that "branch and squash" game just before sending out the next one
camus has joined #linux-sunxi
kaspter has quit [Ping timeout: 260 seconds]
camus is now known as kaspter
<prefixcactus>
do you mean on top of the already-squashed previous revision?
<apritzel>
yes
<apritzel>
so I have the initial feature-devel branch, with all the gory and embarrassing history of how I got there, then feature-v1 with the first version sent out, plus fixes for v2 *on top*, and so on
matthias_bgg has joined #linux-sunxi
gaston1980 has joined #linux-sunxi
\\Mr_C\\ has joined #linux-sunxi
Mangy_Dog has joined #linux-sunxi
<prefixcactus>
apritzel: so you just commit all the fixes into the v1 branch, skipping the devel branch entirely?
<apritzel>
yes
<prefixcactus>
interesting
<apritzel>
I figured it gets too messy and tedious to keep *all* the branches in sync, plus you probably need to rebase anyway (on top of latest master) before each new post
<prefixcactus>
and then branch-squash as before?
<apritzel>
yes
<apritzel>
so when I have fixed all issues in v1, on top of the v1 branch, I branch off -v2, then squash the fixes into the respective commits (with rebase -i)
camus has joined #linux-sunxi
<apritzel>
then check that I didn't mess that up, with "git diff ...-v1", then rebase on top of current master
kaspter has quit [Ping timeout: 265 seconds]
camus is now known as kaspter
\\Mr_C\\ has quit [Quit: (Read error: Connection reset by beer)]
diego71_ has quit [Read error: Connection reset by peer]
Net147 has joined #linux-sunxi
janhenrik has joined #linux-sunxi
bill-auger_ has joined #linux-sunxi
tbueno has joined #linux-sunxi
jerbob92 has quit [Ping timeout: 264 seconds]
Ultrasauce_ has joined #linux-sunxi
mace_ has joined #linux-sunxi
plaes_ has joined #linux-sunxi
mripard has joined #linux-sunxi
matthewcroughan_ has joined #linux-sunxi
Net147_ has quit [Ping timeout: 256 seconds]
bill-auger has quit [Ping timeout: 256 seconds]
Ultrasauce has quit [Ping timeout: 256 seconds]
janhenrik_ has quit [Ping timeout: 256 seconds]
tbueno_ has quit [Ping timeout: 256 seconds]
matthewcroughan has quit [Ping timeout: 256 seconds]
plaes has quit [Ping timeout: 256 seconds]
mace has quit [Ping timeout: 256 seconds]
mripard_ has quit [Ping timeout: 256 seconds]
agraf has quit [Ping timeout: 256 seconds]
agraf has joined #linux-sunxi
nashpa has quit [Ping timeout: 265 seconds]
nashpa has joined #linux-sunxi
hlauer_ has quit [Read error: Connection reset by peer]
hlauer_ has joined #linux-sunxi
Ultrasauce_ is now known as Ultrasauce
diego71 has joined #linux-sunxi
<faruk>
Hi all. How can I create rules on uclibc?
<faruk>
Like udev rules
<faruk>
I want to run a script when a usb is plugged into the device.
DrFrankensteinUK has quit [Ping timeout: 265 seconds]
damex has quit [Quit: damex]
damex has joined #linux-sunxi
<apritzel>
faruk: not sure if "uclibc" makes much sense in this context, as it's just a library, and doesn't tell anything about your environment
<apritzel>
faruk: do you mean you use some minimal system with just busybox, or something made by buildroot?
<apritzel>
then it would be up to that system to provide those services, I don't see why you can't have udev compiled against uclibc, for instance
<apritzel>
faruk: but maybe you reached exactly the limits of "minimal" at this point? And to avoid re-inventing the (complex) wheel, it would be better to upgrade your whole system?
<KotCzarny>
isnt there still hotplug interface in linux?
<KotCzarny>
so one could write simple device actions
damex has quit [Read error: Connection reset by peer]
<faruk>
apritzel: I used buildroot and deliberately chose uclibc. I am trying to set up a system where I can run a script with wireless and usb-ethernet smaller than 9MB.
damex has joined #linux-sunxi
<faruk>
apritzel: I preferred it because the size of uclibc is very small.
Guest49163 has quit [Ping timeout: 276 seconds]
<apritzel>
faruk: sure, but this is a buildroot problem then, has nothing to do with uclibc
<apritzel>
does buildroot offer to build udev?
<apritzel>
eudev?
<faruk>
apritzel: I did not fully understand what you mean
<mripard>
faruk: you can use busybox' mdev
<faruk>
mripard: I tried mdev but I was not succesfully. If it's possible to do this with mdev I probably skipped something. Because it's the first time I'm trying to do something like this
damex has quit [Read error: Connection reset by peer]
damex has joined #linux-sunxi
<faruk>
apritzel: I think I understand what you mean. After selecting uclicb, buildroot suggests mdev.
<faruk>
Thanks for helping
faruk has quit [Quit: Leaving]
faruk has joined #linux-sunxi
damex has quit [Read error: Connection reset by peer]
damex has joined #linux-sunxi
damex has quit [Read error: Connection reset by peer]
damex has joined #linux-sunxi
camus has joined #linux-sunxi
kaspter has quit [Remote host closed the connection]
camus is now known as kaspter
JohnDoe_71Rus has joined #linux-sunxi
hlauer_ has quit [Read error: Connection reset by peer]
reinforce has quit [Quit: Leaving.]
hlauer_ has joined #linux-sunxi
mmarc__ has quit [Remote host closed the connection]
mmarc__ has joined #linux-sunxi
zoobab has quit [Ping timeout: 260 seconds]
zoobab has joined #linux-sunxi
megi has quit [Quit: WeeChat 3.0.1]
megi has joined #linux-sunxi
cmeerw has joined #linux-sunxi
gaston1980 has quit [Quit: Konversation terminated!]