Leaves me unsure as to which firmware version source I am downloading to edit. 266.22 beta1? 266.,24 beta2, 270.xxx? Obvious question to you, but to me I'd probably end up making a "new" firmware from some derelict code by accident and creating more problems than I resolve.
Until I see some major glitches with my firmware just yet, I will continue using the firmware you made for me. Thanks again.
The only issue I am having currently is my blu-ray player does not like the dynamic IP assignment from my router and requires a full reboot every 3-4 weeks to fix internet access. It's entirely the blu-ray players fault and nothing to do with the firmware AFAIK.
Leaves me unsure as to which firmware version source I am downloading to edit. 266.22 beta1? 266.,24 beta2, 270.xxx? Obvious question to you, but to me I'd probably end up making a "new" firmware from some derelict code by accident and creating more problems than I resolve.
All that command does is download the latest code from the Asuswrt-Merlin repository. It won't necessarily have a build number to it, it'll just be the most recent code that Eric has committed and pushed to the repository, if that makes sense.
Do keep in mind that the code might not necessarily be in a working state at any given time - the build may just fail outright, or it might not work on the router, or it might not work as expected - any number of things can go wrong. Not to scare you off - it's definitely cool that you've taken the interest in building the software yourself - but it's definitely something to keep in mind. Luckily for you, however the RT-N66U is practically unbrickable with a recovery mode that'll let you reflash firmware if something goes wrong, so unless you're tinkering with your CFE you should be fine.
@RMerlin: it might be helpful to tag releases in git, so if others want to apply patches to fix certain issues, they can have stable codebases to work off of rather than pulling the latest code which might not be ready for prime time usage just yet.
@RMerlin: it might be helpful to tag releases in git, so if others want to apply patches to fix certain issues, they can have stable codebases to work off of rather than pulling the latest code which might not be ready for prime time usage just yet.
I tried to do it for a while but couldn't get into the discipline of doing it constantly. I'll see what would work best with Github.
Sent from my Nexus 7 using Tapatalk HD
__________________
Asuswrt-Merlin: Customized firmware for Asus routers Github: github.com/RMerl - Twitter: RMerlinDev
See the sticky post for more info.
I'll guess have to just bribe either Merlin or TeHashX with paypal donations or sexual favors to include this sony dlna fix on future firmware releases.
I'll guess have to just bribe either Merlin or TeHashX with paypal donations or sexual favors to include this sony dlna fix on future firmware releases.
Need to be sure it won't break other devices - that's the actual important thing.
__________________
Asuswrt-Merlin: Customized firmware for Asus routers Github: github.com/RMerl - Twitter: RMerlinDev
See the sticky post for more info.
git tag -a 3.0.0.4.266.24 -m "Release version 3.0.0.4.266.24"
git push --tags
is generally how I do it on GitHub.
Can a clone be specified a tag? That's where I wasn't sure if it would make cloning a stable copy easier, or would be better off having a separate Stable branch to which I would push whenever I release a new stable version.
I might start looking at a few other big Github projects (like XBMC) to see how they handle it on their end.
But tagging would definitely be a good idea, if only for making it easier to figure out important points in the timeline.
__________________
Asuswrt-Merlin: Customized firmware for Asus routers Github: github.com/RMerl - Twitter: RMerlinDev
See the sticky post for more info.
git clone git://github.com/RMerl/asuswrt-merlin.git
git tag -l (optional, lists all tags)
git checkout 3.0.0.4.266.24
Also, GitHub allows to download tarballs and zipped versions of the repository at that particular tag, so instead of cloning the repo, they could just download an extract a tarball. I'm not sure if you could then do a fetch and merge in newer changes from that, or if you're stuck with that particular tagged code. I've never tried.
The Following User Says Thank You to got_milk For This Useful Post:
git clone git://github.com/RMerl/asuswrt-merlin.git
git tag -l (optional, lists all tags)
git checkout 3.0.0.4.266.24
That looks like an acceptable solution to me. Just need to document it on the Wiki for easy access to newcomers. Using branches might prove to be more confusing than tags (since branches in the Github concept aren't exactly the same thing people are used to in other RCS).
Quote:
Originally Posted by got_milk
Also, GitHub allows to download tarballs and zipped versions of the repository at that particular tag, so instead of cloning the repo, they could just download an extract a tarball. I'm not sure if you could then do a fetch and merge in newer changes from that, or if you're stuck with that particular tagged code. I've never tried.
That would probably imply including the history or at least some other metadata to allow one to do a pull afterward. Probably cleaner to rely on tags IMHO.
__________________
Asuswrt-Merlin: Customized firmware for Asus routers Github: github.com/RMerl - Twitter: RMerlinDev
See the sticky post for more info.
Linear Mode
