svn up usually does the trick. The only case that can confuse things
is if you have local changes. You can do 'svn revert -R .' to get
back to the base versions and then 'svn up'.
Rick
On Jan 20, 2009, at 8:17 AM, Dean Glazeski wrote:
For some reason, it appears the svn update isn't work
For some reason, it appears the svn update isn't working. A fresh check
out of the repository and everything looks good. I'm probably doing
something wrong during the update. Is there a standard way to update my
working copy once you commit changes that I made? Thanks.
// Dean
Rick Altherr
In my copy of the repo, at91sam9260.cfg is what at91sam9260minimal.cfg
was. In fact, the checkin shows that at91sam9260.cfg was replaced.
The fix in unknown-board-atmel-at91sam9260.cfg is still necessary.
Committed in r1353.
Rick
On Jan 19, 2009, at 11:52 PM, Dean Glazeski wrote:
It loo
It looks like this patch didn't get applied quite right on r1350. It
appears that at91sam9260.cfg is the same as before, but
at91sam9260minimal.cfg is now gone. I went ahead and got the old
minimal config down and changed the at91sam9260.cfg file. There was
also a mistake I left in the 'unkn
Committed in r1350.
Rick
On Jan 17, 2009, at 1:39 AM, Dean Glazeski wrote:
I went ahead and did some moving of some files relating to the
AT91SAM9260 and the Olimex SAM9-L9260 development board. I also
created another file for the Olimex JTAG TINY that doesn't include
the 'A'. Apparent
I went ahead and did some moving of some files relating to the
AT91SAM9260 and the Olimex SAM9-L9260 development board. I also created
another file for the Olimex JTAG TINY that doesn't include the 'A'.
Apparently, the description for the JTAG tiny can differ between Windows
and Linux Operati
